Using the fitplot=true option causes incorrect PS output. For example, the attached 'print.ps' is from Mozilla, looking at cups.org. 'lpr -ofitplot=true print.ps' fails for me, and in the logs I see:
OK, the problem is cause by how they are using the Begin/EndPageSetup comments - they basically are saving the graphics state and scaling the whole page, not doing Begin/EndFeature comments and commands.
Unfortunately, this is something that Adobe has documented as "good practice", even though it is a MAJOR pain to work around...
Please note: Mozilla's output also contains a setpagedevice command without a corresponding Begin/EndFeature pair, which might cause problems with some printers...
Version: 1.2rc1
CUPS.org User: twaugh.redhat
Using the fitplot=true option causes incorrect PS output. For example, the attached 'print.ps' is from Mozilla, looking at cups.org. 'lpr -ofitplot=true print.ps' fails for me, and in the logs I see:
Error: /undefined in pagelevel
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval--
Dictionary stack:
--dict:1138/1686(ro)(G)-- --dict:1/20(G)-- --dict:93/200(L)--
Current allocation mode is local
Last OS error: 2
ESP Ghostscript 815.01: Unrecoverable error, exit code 1
The text was updated successfully, but these errors were encountered: