Hi Kevin,
I did about the research I could on the different printer models.
By the way, what is your printer model? Is there any way you could test
the original (bad) PS file using CUPS with a different kind of printer?
It's conceivable that the printer is ignoring Begin(Page)Setup ...
Frank Dohrmann wrote:
Result:
The original file does not print (correctly) on the following models:
TekPhaser 740, Laserjets 2300, 2200, 2420, 4M, Lexmark Optra R+, Deskjet 600.
The only printer it printed on correctly was
Laserjet 3700
The fix prints on all of the printers.
For
Package: paw
Version: 2004.11.04-3
When I produce a postscript file from paw and print it afterwards, I get
either a blank sheet or a corner of a too large object. I.e. I do
paw fun1 1 sin(x) 100 0. 3.
paw pic/pri paw.ps
paw exit
$ lpr paw.ps
only after some postprocessing
$ ps2ps paw.ps
Hi Frank,
Frank Dohrmann wrote:
When I produce a postscript file from paw and print it afterwards, I get
either a blank sheet or a corner of a too large object. I.e. I do
paw fun1 1 sin(x) 100 0. 3.
paw pic/pri paw.ps
paw exit
Just to make sure I know what you are doing, before the
Hi Kevin,
I use
PAW graphics/opt zfl1
PAW fun1 1 sin(x) 100 0. 3.
PAW pic/print paw.ps
Does it make any difference if you manually edit a copy of the original
PAW-created postscript file so that the above lines instead read as follows
[...]
%%EndProlog
%%Page: number 1
Frank Dohrmann wrote:
%%EndProlog
%%BeginSetup
%%EndSetup
newpath gsave 20 28 t .25 .25 scale gsave
%%Page: number 1
and that one prints fine via cups on the postscript printer.
Interesting. I've just tested that a PS file hacked in this way still
looks OK in GV and when printed via
Hi Kevin,
By the way, what is your printer model? Is there any way you could test
the original (bad) PS file using CUPS with a different kind of printer?
It's conceivable that the printer is ignoring Begin(Page)Setup ...
End(Page)Setup sections rather than CUPS ignoring them.
I used two
7 matches
Mail list logo