Apache OpenOffice (AOO) Bugzilla – Issue 8068
OOo postscript output breaks mpage
Last modified: 2003-03-12 14:43:12 UTC
Using mpage version 2.5.1pre2. Catting postscript generated by OOo through mpage -2 causes ghostview to barf. cat OOo_output.ps | mpage -2 > page.ps gv page.ps gives an error: "Error: /rangecheck in .installpagedevice Operand stack: --dict:46/46(ro)(G)-- --nostringval-- 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 .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1032/1476(ro)(G)-- --dict:0/20(G)-- --dict:105/200(L)-- Current allocation mode is local GNU Ghostscript 6.51: Unrecoverable error, exit code 1 " The error can vary but the result is the same. mpage -2 is supposed to put two pages on a single sheet but the result with OOo postscript is the first page on a single sheet while the remaining pages are properly formatted. Any other postscript appears fine. To reproduce: 1. Create a print queue using the following printcap entry: booklet:\ :ml=0:\ :mx=0:\ :sd=/var/spool/lpd/booklet:\ :af=/var/spool/lpd/booklet/booklet.acct:\ :sh:\ :lp=|/var/spool/lpd/booklet/booklet-print: 2. install the attached booklet-print script as the print filter. While "LOGFILE" is defined, the filter will generate a file called "book.ps" which will cause the error. 3. Use OOo spadmin to create a "Generic Printer" pointing to this print spool 4. Create anything in Writer or Calc (that's all I tested with) (even blank) and print to this printer. 5. use "gv /var/spool/lpd/booklet/book.ps" to view
Created attachment 3064 [details] Print filter script
reassign
I cannot reproduce gs error. I printed 3 pages to file, did mpage -2 >bla.ps and got 2 pages of output; the original first page did not show, but this is due to issue 5456. What version did you actually use ? I tried with OOo 1.0.1 and 644.
Found problem with 1.0.0 Will test with 1.0.1 later. When will issue 5456 be fixed? Thanks
when i know what actually upsets mpage.
The problem of mpage's output is that it does not filter the DSC compliant printer specific features which are bracketed by %%BeginFeature/%%EndFeature pairs. These features enable things like duplex, hardware resolution, media size, etc. and should be either eliminated by mpage or the original code should be bracketed by %%BeginDocument/%%EndDocument pairs (see also issue 5456). This can only be fixed by mpage, not by OOo.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.