Issue 22389 - Postscript output is not DSC conforming
Summary: Postscript output is not DSC conforming
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 1.1.1
Assignee: Joost Andrae
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-12 19:29 UTC by pmladek
Modified: 2004-01-16 15:53 UTC (History)
2 users (show)

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

Attachments
This patch fixed the problem for us. (621 bytes, patch)
2003-11-12 19:34 UTC, pmladek 		no flags Details | Diff
This patch fixed the problem for us. (621 bytes, patch)
2003-11-12 20:04 UTC, pmladek 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description pmladek 2003-11-12 19:29:01 UTC 
The OOo generates the folowing lines, in the Poscript output, which
are not DSC conforming:

showpage
grestore grestore
%%PageTrailer

---cut from DSC---
If the showpage operator is used in combination with save and restore,  the
showpage should occur after the page-level restore operation. The motivation for
this is to redefine the showpage operator so it has side  effects in the printer
VM, such as maintaining page counts for printing n-up  copies on one sheet of
paper. If showpage is executed within the confines of  a page-level
save-restore, attempts to redefine showpage to perform extra  operations will
not work as intended. This also applies to the BeginPage and  EndPage parameters
of the setpagedevice dictionary. The above discussion  also applies to
gsave-grestore pairs.
---cut from DSC---

According to the DSC the operator showpage should be moved after grestore.


The current state makes problems on some printers. For example we have
problems to use the native HPnup ability from HP_LaserJet_4050_Series.ppd.
If we try to print a postscript generated by OOo as two pages per sheet
then each second page is printed over the first one.
Comment 1 pmladek 2003-11-12 19:34:31 UTC 
Created attachment 11199 [details]
This patch fixed the problem for us.
Comment 2 pmladek 2003-11-12 20:04:59 UTC 
Created attachment 11200 [details]
This patch fixed the problem for us.
Comment 3 pavel 2003-11-13 06:32:05 UTC 
Confirmed. Redbook (second edition), page 628 at the bottom.

Set target to 1.1.1 because this is very simple.
Comment 4 christof.pintaske 2003-11-13 10:36:12 UTC 
cp->pl: please have a look at it and verify that this is really the
page level restore (there are two). 1.1.1 is only acceptable if there
is no danger of regression.
Comment 5 christof.pintaske 2003-11-13 10:43:30 UTC 
.
Comment 6 philipp.lohmann 2003-11-13 16:00:17 UTC 
accepting
Comment 7 philipp.lohmann 2003-11-13 16:00:46 UTC 
fixed in CWS vcl7pp1r3
Comment 8 philipp.lohmann 2003-11-13 16:04:39 UTC 
pl->us: please verify in CWS vcl7pp1r3
Comment 9 sergiomb 2003-11-26 04:53:37 UTC 
this can generate two blank pages at begging of printing ?
with OOo 1.1 I had this problem .
OOo generate a ps (or printing direcly) that when I send to print
gives me the 2 pages in blank before printing correctly.
with other application I don't have this problem.
thanks in advance
Comment 10 ulf.stroehler 2003-12-16 13:41:18 UTC 
US->JA: could you pls. take over.
Come back to me or PL if you have questions.
Comment 11 Joost Andrae 2003-12-17 11:37:53 UTC 
JA: verified in vcl7pp1r3 cws. The command "showpage" now appears after the two
"grestore"'s.
Comment 12 Joost Andrae 2003-12-17 11:38:09 UTC 
.
Comment 13 Joost Andrae 2004-01-16 15:53:53 UTC 
JA: verified within integration build src645m25s1. Closing issue