Summary: | Can't convert PDF to image | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | v.ripoll |
Component: | PDF Interpreter | Assignee: | Ken Sharp <ken.sharp> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | santoshjogade.99 |
Priority: | P4 | ||
Version: | 9.20 | ||
Hardware: | PC | ||
OS: | Windows 10 | ||
Customer: | Word Size: | --- | |
Attachments: | The PDF that can't be converted to an image. |
Description
v.ripoll
2017-03-08 05:11:37 UTC
Adobe Acrobat is unable to open this PDF file it throws an error 'expecting a name object'. Looks to me like your file is simply broke. Indeed, I work with Foxit PhandomPDF and it opens it just fine. When I tried with Adobe Acrobat Reader DC, I got an error (18). I will investigate in that direction. I confirm this issue can be closed. The PDF document was not properly created (even though it opens without error in Foxit PhantomPDF). FWIW, the problem here is that the page dictionary defines an XObject Resource 'XF1': /Xf1 1 0 R But object 1 is defined as an ICC profile: 1 0 obj << /Alternate /DeviceCMYK /N 4 /Length 557168 >> stream which is used by object 2 as a colorspace resource: 2 0 obj << /Type /XObject /Subtype /Image /Width 19 /Height 24 /Length 1824 /ColorSpace [ /ICCBased 1 0 R ] /BitsPerComponent 8 >> Clearly the definition of the XObject in the page Resources dictionary is incorrect, but the page stream uses that XObject: q 0.033333 0 0 0.033333 0.236378 0.25348 cm /Xf1 Do Q This means that the PDF consumer would have to treat an ICC profile as an image. Obviously it can't do that. Presumably Foxit simply (and silently!) ignores the error and fails to draw that image XObject. Removing the spurious entry from the page resources dictionary and the use from the content stream, results in a file which all the PDF consumers I have will open without error. |