Issue 7790 - Output postscript fails to be interpreted.
Summary: Output postscript fails to be interpreted.
Status: CLOSED DUPLICATE of issue 7262
Alias: None
Product: gsl
Classification: Code
Component: www (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: philipp.lohmann
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-19 13:34 UTC by Unknown
Modified: 2003-03-11 17:54 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-09-19 13:34:41 UTC
The message below was posted to the user mailing list but I've gotten no luck. I
have determined that other people are having the same problem but I can't figure
out who the lucky ones are and aren't. Some Red Hat people fail and some
Mandrake people fail. I'm running cups, but I can't even view the PostScript
with gv or ghostview. And the weird thing is that people can send me a Word doc
and that will print ok. So it simultaneously looks like it's a problem with OOo,
ghostview, *and* my printer. None of this makes any sense. Please let me know if
there's anything I can do to provide more info.

Since noone is answering my question, maybe I can get some more info from 
another approach: Could someone please create a new document that just has 
the word hello in it and then please send me the .sxw file and their 
resulting PostScript file? Maybe I can look at the difference bewteen your 
resulting Postscript and mine. :-(

On Sat, 14 Sep 2002, Steven W. Orr wrote:

=>I can not print from OO if I create a document. Here's the whole story.
=>
=>I create a truly minimal document which only says the word Hello. 
=>
=>Before saving it I go to print it to a file. The file is called x1.ps
=>It can be found at http://steveo.syslang.net/ootst/x1.ps
=>
=>I go to view that file with gv under linux. gv will not display the file 
=>complaining:
=>
=>X Error of failed request:  BadMatch (invalid parameter attributes)
=>  Major opcode of failed request:  73 (X_GetImage)
=>  Serial number of failed request:  36
=>  Current serial number in output stream:  36
=>
=>So then I save the file as an sxw (native format) and restart OO with the 
=>saved file. Once again I print to a file. This time you can see it as 
=>http://steveo.syslang.net/ootst/x2.ps
=>Also, the sxw file is at
=>http://steveo.syslang.net/ootst/x1.sxw
=>
=>But, trust me, it only differs by the date internally.
=>
=>I even save it as a Word doc file
=>http://steveo.syslang.net/ootst/x1.doc
=>
=>and try to print from that which yields
=>http://steveo.syslang.net/ootst/x4.ps
=>No difference.
=>
=>Now the fun: I view x1.ps using kghostview and for some magic reason, that 
=>works. From there, I print to PDF format which yields
=>http://steveo.syslang.net/ootst/x2.pdf
=>
=>I can view x2.pdf just fine using xpdf and from there I can print to x3.ps 
=>which *is* viewable by gv. (BTW, gv is just a pretty front end to 
=>ghostview. And also, they perform identically.) X3.ps can be seen here:
=>http://steveo.syslang.net/ootst/x3.ps
=>
=>I happen to be running Red Hat 7.3 with jre-1.3.1 and OO 1.0.1. I happen 
=>to be running CUPS instead of LPRng.
=>
=>And just one more little item, just to screw you up even further: If 
=>someone sends me a uSoft Word doc, it will print just fine. So it seems 
=>that the only problems I'm having are the docs that I try to create 
=>myself. 
=>
=>Also, my printer seems to be working fine. The resolution is properly set 
=>to PostScript at 600 DPI in both CUPS and in OO.
=>
=>I really need this working and I don't have the vaguest clue how to fix 
=>it. Someone, please?
Comment 1 philipp.lohmann 2002-11-12 14:40:12 UTC
reassign
Comment 2 philipp.lohmann 2002-11-12 17:54:57 UTC
The problem with PostScript viewers is due to i1894 and i7262. To make
the output in gv work you can de-select "Respect document structure"
in the "State" menu of gv. Unless you have a problem actually printing
i'd say this is duplicate to those issues.
Comment 3 philipp.lohmann 2003-01-24 14:09:56 UTC
this is a duplicate

*** This issue has been marked as a duplicate of 7262 ***
Comment 4 michael.bemmer 2003-03-11 17:15:54 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 5 michael.bemmer 2003-03-11 17:54:28 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.