Issue 5456 - unable to "2up" produced PostScript
Summary: unable to "2up" produced PostScript
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Linux, all
: P3 Trivial with 2 votes (vote)
Target Milestone: AOO PleaseHelp
Assignee: philipp.lohmann
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-31 15:44 UTC by gurubert
Modified: 2003-07-29 10:22 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
PostScript as it comes out of OpenOffice.org (242.33 KB, application/postscript)
2002-05-31 15:46 UTC, gurubert
no flags Details
the same document after running "mpage -2 print.ps > print2.ps" (247.09 KB, application/postscript)
2002-05-31 15:46 UTC, gurubert
no flags Details
The two files (I had trouble attaching files...) (9.39 KB, application/octet-stream)
2002-06-18 09:48 UTC, rmano
no flags Details
bugdoc 1 converts fine (245.26 KB, text/plain)
2003-06-24 09:48 UTC, christof.pintaske
no flags Details
bugdoc-2 converts fine, too (20.30 KB, text/plain)
2003-06-24 09:50 UTC, christof.pintaske
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description gurubert 2002-05-31 15:44:44 UTC
When printing to a PostScript file with the generic postscript driver the postscript code seems to be not quite correct.
If a "mpage -2" is applied to the produced postscript the first page does not get printed. It seems to be drawed under the second page.
Comment 1 gurubert 2002-05-31 15:46:02 UTC
Created attachment 1825 [details]
PostScript as it comes out of OpenOffice.org
Comment 2 gurubert 2002-05-31 15:46:56 UTC
Created attachment 1826 [details]
the same document after running "mpage -2 print.ps > print2.ps"
Comment 3 thorsten.martens 2002-06-03 09:46:49 UTC
TM->HI: As talked to you, please have a look, thanks !
Comment 4 moritzmhq 2002-06-04 11:05:35 UTC
I can confirm the error. It also comes up in the kde printing  
system, which uses psnup as filter to print several pages on one 
sheet (like Windows Fineprint). 
  
If you let the postscript be rewritten by e.g. ghostscript, psnup  
works fine afterwards. 
  
Also for some reason the Postscript output starts with page number  
"0" instead of "1". I do not know if this is related, but it should  
be corrected as well.  
Comment 5 h.ilter 2002-06-17 13:38:28 UTC
Seems to be a case for you.
Comment 6 philipp.lohmann 2002-06-17 14:07:01 UTC
Could you please be a bit more specific what about the PostScript code
should be different ? The PostScript code produced by OpenOffice.org
is valid in itself as you can see from the fact that it runs with
ghostscript and a multitude of different PostScript interpreters built
into as many printers. If any tool of your choice meddles with the
PostScript and does not work as advertised, why do you think the
problem is on Ooo's side ?
Comment 7 gurubert 2002-06-17 14:11:40 UTC
Hi!

I do not speak PostScript myself, but the PostScript produced by OOo fails to be 2up*ed by the tools we tried (krpinter, 
mpage). And these tools are able to produce 2up'ed documents when used with other PostScript files.
What is your favorite tool to do this task?
Comment 8 philipp.lohmann 2002-06-17 14:17:39 UTC
File->PageView allows for setting up an arbitrary number of pages
printed on one. Still if you can tell me what needs to be done to work
with mpage i can probably change the produced PostScript code that way.
Comment 9 gurubert 2002-06-17 16:14:06 UTC
There is now menu item File->Pageview for presentations, or am I wrong? How do you print presentations two or more slides on 
one page?
Comment 10 philipp.lohmann 2002-06-17 17:36:51 UTC
That is true. I'll try to find out what the problem between mpage and
Ooo is.
Comment 11 rmano 2002-06-18 09:44:59 UTC
The attached file prints fine, but when printed to a file triggers 
an error on gv:

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  73 (X_GetImage)
  Serial number of failed request:  33
  Current serial number in output stream:  33

But not on gs... this is most strange. I attach two files: the .sxw 
and the produced "print to file" .ps. Hope this helps...
Comment 12 rmano 2002-06-18 09:48:37 UTC
Created attachment 2011 [details]
The two files (I had trouble attaching files...)
Comment 13 philipp.lohmann 2002-06-18 10:01:24 UTC
Sorry, but gv catching an Xerror is gv's problem, not ours. An Xerror
means gv requested something from the Xserver it shouldn't have.
Comment 14 gurubert 2002-08-08 14:56:32 UTC
StarOffice 6.0 with the latest patch does have the same issue.
Comment 15 philipp.lohmann 2003-01-23 12:07:48 UTC
After some experimentation i found out that mpage's PostScript output
is  not DSC conformant; the problem can be solved by excluding all
code bracketed by %%BeginFeature/%%EndFeature pairs. Between these
pairs there is printer specific code for special features (duplex on,
select A4 paper, etc); the canonical way would be for mpage to enclose
the pages in %%BeginDocument/%%EndDocument pairs or simply removing
the %%BeginFeature/%%EndFeature pairs and everything in between.

Anyway this can only be fixed by the PostScript manipulation tools
(mpage,psnup), not by OOo.
Comment 16 michael.bemmer 2003-03-12 14:17:07 UTC
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.
Comment 17 michael.bemmer 2003-03-12 14:17:29 UTC
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.
Comment 18 michael.bemmer 2003-03-12 14:35:17 UTC
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. 
Comment 19 bulbul 2003-05-24 23:37:10 UTC
Using kprinter, i cannot print OOo documents two-to-a-page. Is this
the same bug? Does kprinter use mpage to print two-to-a-page?
Comment 20 bulbul 2003-05-25 00:08:27 UTC
I have contacted the mpage maintainer about this problem and have
referred him to this page.
Comment 21 philipp.lohmann 2003-05-27 12:51:01 UTC
i don't know what printer does; but probably something similar to mpage
Comment 22 bulbul 2003-05-27 17:04:21 UTC
Just as follow-up, although i sent a message to the mpage mainter, he
has not responded.

As for kprinter, it does not use mpage, so it must implement the same
funcionality on its own.

I will look into posting a bug on the kprinter Bugzilla. This is a
rather big problem. I think that many people will try to print
multiple OOo pages to a sheet using KDE. Currently it is not possible.
Comment 23 gurubert 2003-06-23 14:32:17 UTC
Hi!

I still think this is caused by the PostScript code produced by OOo.

Is anybody able to do a duplex printing using the PostScript output of
OOo? 
Comment 24 philipp.lohmann 2003-06-23 14:39:45 UTC
I still don't think so :-)

Do you have any hard data ?
Comment 25 gurubert 2003-06-23 14:44:02 UTC
Hi!

I do not have any hard data. This is just a observation that the only
PostScript causing this error comes from OOo. And this makes it very
inconvenient to print large documents.
Comment 26 christof.pintaske 2003-06-24 09:48:41 UTC
Created attachment 7086 [details]
bugdoc 1 converts fine
Comment 27 christof.pintaske 2003-06-24 09:50:04 UTC
Created attachment 7087 [details]
bugdoc-2 converts fine, too
Comment 28 christof.pintaske 2003-06-24 09:56:30 UTC
both of your bugdocs can be converted quite fine to two-on-one page
using pstops (out of psutils). I have no issues to view the converted
files with ghostscript or to print them out. 

If there is an issue with kprinter or mpage I really recommend to ask
the respective author to have a look at the problem.
Comment 29 philipp.lohmann 2003-07-29 10:22:42 UTC
Since there do not seem to be any points left on this i'll close this
issue.