Issue 8119 - Postscript level 1 problems.
Summary: Postscript level 1 problems.
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: gsl
Classification: Code
Component: www (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: issues@gsl
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-07 13:53 UTC by Unknown
Modified: 2003-03-12 14:40 UTC (History)
1 user (show)

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

Attachments
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 Unknown 2002-10-07 13:53:55 UTC 
No matter how Often I set the printer to postscript level 1 no color and 300 bpi
under staroffice writer, it keeps on sending illegal postscript code to my
printer. Even though under spadmin the test page does print correctly.
When I ask my printer to print out the offending command it gives me the
following postscript error message: 

ERROR: undefined
on command : setpagedevice
Stack : -dict-- , en_of_stack 

My printer settings are as follows:
Generic printer
Papersize : A4
prientation : portrait
Duplex : <ignore>
Scale : 1
Resolution : 300
Manual Feed : False
Postscript Level : 1
Color : Grayscale
Color Depth : 24

This gives me a correct printout under spadmin, but does not give me a correct
printout under openoffice writer 1.0.1

Monchi.
--
Comment 1 philipp.lohmann 2002-11-12 14:49:50 UTC 
reassign
Comment 2 philipp.lohmann 2002-11-12 14:57:50 UTC 
Please use another PPD than "Generic Printer" (SGENPRT.PS), e.g. use
"Apple LaserWriter-Select 310" which is a PPD for a real PostScript
Level 1 printer. The language level switch only influences the actual
PostScript commands used, but cannot change the printer specific
commands to set page sizes, paper trays, etc.. Please use the correct
PPD for your printer if possible.
Comment 3 michael.bemmer 2003-03-12 14:22:20 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 4 michael.bemmer 2003-03-12 14:22:45 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 5 michael.bemmer 2003-03-12 14:22:50 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 6 michael.bemmer 2003-03-12 14:40:22 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 7 michael.bemmer 2003-03-12 14:40:40 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.