Bug 692585 - PDF output mangles clipping path
Summary: PDF output mangles clipping path
Status: RESOLVED WORKSFORME
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Writer (show other bugs)
Version: 9.04
Hardware: PC Linux
: P4 normal
Assignee: Ken Sharp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-12 16:40 UTC by John Haltiwanger
Modified: 2011-10-12 17:53 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---


Attachments
Generative design in an EPS file. Re-interpret for different results. (3.81 KB, application/postscript)
2011-10-12 16:40 UTC, John Haltiwanger
Details
non-generative example (630 bytes, application/postscript)
2011-10-12 16:45 UTC, John Haltiwanger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Haltiwanger 2011-10-12 16:40:17 UTC
Created attachment 7984 [details]
Generative design in an EPS file. Re-interpret for different results.

When invoking `gs -sDEVICE=pdfwrite -sOutputFile=myfile.pdf -dBATCH -dNOPAUSE complex.eps`, the generated PDF shows strokes outside of established clipping paths.

The input file is an EPS file which prints fine when sent directly to a PostScript printer. This leads me to believe that, however sloppy the code may or may not be from a professional PS perspective, it is not the input file which is at fault.

Please note that the EPS is a generative design. If the reported bug is not displayed when you first invoke gs, _please_ repeat: some of the patterns in the EPS file exhibit less or none of the abherrent artifacts.
Comment 1 John Haltiwanger 2011-10-12 16:45:03 UTC
Created attachment 7985 [details]
non-generative example
Comment 2 Chris Liddell (chrisl) 2011-10-12 17:06:53 UTC
Ghostscript, Acrobat, xpdf, Jaws and Harlequin all render the Ghostscript/pdfwrite produced PDF correctly. The *only* viewer I can find that gets it *wrong* is evince.

This leads me to believe it is an evince/poppler bug, rather than a pdfwrite problem (which is interesting as poppler is a fork of xpdf!).
Comment 3 Chris Liddell (chrisl) 2011-10-12 17:53:30 UTC
Reporter agrees with my conclusion - closing........