Summary: | Adobe Distiller cannot process PostScript file generated by pdftocairo | ||
---|---|---|---|
Product: | cairo | Reporter: | Alex Korobkin <korobkin+lpad> |
Component: | postscript backend | Assignee: | Adrian Johnson <ajohnson> |
Status: | RESOLVED FIXED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | cloos |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
gezond.pdf
gezond.ps gezond2.ps - with indents |
Description
Alex Korobkin
2014-10-08 19:20:56 UTC
Created attachment 107577 [details]
gezond.pdf
Created attachment 107578 [details]
gezond.ps
[Email replies are broken; re-submitting.]
> %%[ Error: undefined; OffendingCommand: .& ]%%
> %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
> %%[ Warning: PostScript error. No PDF file produced. ] %%
The only place .& occurs in that postscript is at the end of the image.
Which implies that the image data may be longer than required, or that
adobe's current software expects the /ASCII85Decode data to have no
extra whitespace (the file leads each line in the ascii85 data with a
space).
For a test, try running:
:; perl -pe 's/^ //' <gezond.ps >gezond2.ps
and then sending gezond2.ps to distiller or a printer.
If that works, then the indent is the imcompatibility.
If it does not work, then perhaps the pdf has extraneous data in the
image, and cairo copies all of it, rather than limiting the data to
the minimum necessary? (Just speculating.)
Created attachment 107671 [details]
gezond2.ps - with indents
Thanks for the suggestion, here is the file that I've got. Unfortunately, it still produces exactly the same error.
This should fix this issue: https://cgit.freedesktop.org/cairo/commit/?id=0e6f7deac1092666464b81866f5d5a13866befe4 It indeed fixes the issue! Thanks for looking into this, you're awesome. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.