Summary: | PostScript with Zapfino fails | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Jack Moffitt <jack> |
Component: | PS Interpreter | Assignee: | Ralph Giles <ralph.giles> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | master | ||
Hardware: | All | ||
OS: | All | ||
Customer: | Word Size: | --- | |
Attachments: | PostScript generated by Acrobat 5.0.6 |
Description
Jack Moffitt
2002-10-17 01:17:37 UTC
Comment originally by oneiros@users.sourceforge.net Logged In: YES user_id=33472 This works in 7.31; now only the bbox-device reports nothing with this file. Comment originally by alexcher@users.sourceforge.net Logged In: YES user_id=65750 This is a known problem. it is analysed in detail in http://www.ghostscript.com/pipermail/gs-devel/2002-August.txt The file runs with gswin32 -c save pop -f ampersand.ps Created attachment 71 [details]
PostScript generated by Acrobat 5.0.6
I recommend 'false 0 startjob pop' as the preferred method to start Ghostscript as if under a job server. Linux printing should use this to process files to avoid problems with files that expect to run on printers. The command line invocation is: -c "false 0 startjob pop" -f With Ghostscript 8.11 and later, applications invoking ghostscript in a printing context need to also specify -dNOOUTERSAVE to disable another work-around for files that expect to run in a jobserver environment. See http://www.ghostscript.com/pipermail/gs-cvs/2003-July/003465.html for details. This has been kept open as a place holder for education efforts re the job server options. The title is confusing, so I've created a new bug 687095 to track that and am closing this one. |