GhostScript - latest version Problem with opening the some PDF files. But file can be processed by 8.56. How to send requested files to you?
Created attachment 4584 [details] Problem with converting.
The revision that broke this file was r7795; unfortunately the log message is useless: ------------------------------------------------------------------------ r7795 | tim | 2007-03-23 06:56:11 -0700 (Fri, 23 Mar 2007) | 1 line Custom color hooks code merge ------------------------------------------------------------------------ and the svn diff -r7994:7995 output is 7000+ lines.
BTW, the command line I'm using for testing: bin/gs -sDEVICE=pbmraw -sOutputFile=test.pbm ./690161.pdf
The PDF file is invalid. It has spurious '>>' tokens between 'endstream' and 'endobj'. endstream >> endobj Currently, Ghostscript cannot repair this kind of damage. To repair the file replace '>>' with 2 spaces ' ' to keep the object offsets intact.
Created attachment 4594 [details] Problem with converting.
The file attached as the comment #5 is unrelated to the comment #1. Please file a separate bug report next time. Fortunately the bug is easy to fix. Add the support of null entries in /Annots array. See: http://ghostscript.com/pipermail/gs-cvs/2008-November/008798.html The patch is committed as a rev. 9219. Regression testing shows no differences; we had no such files before.
Created attachment 4611 [details] patch for the 1st problem. Add a check for bogus '>>' after 'endstream' to recover files generated by 'Kroll Background Screening'. The patch is committed as a rev. 9235. Regression testing shows no differences.
How to get new (fixed) version?
You'll have to check out a copy from the svn repository. See http://svn.ghostscript.com/ for more information.
I can't find the link to latest installation file (GhostScript). Send me please.
The latest release is available from http://sourceforge.net/project/showfiles.php?group_id=1897&package_id=108733
It's the old version (2008-08-01 21:38) without my requested fix.
The next release is scheduled for February and should contain the fix. Otherwise, there is enough information here to find and apply the fix yourself, or to check out the development source code from our repository. Good luck.