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 above commands
you did something like

PAW > pic/create paw
PAW > pic/switch z

right?


> $ lpr paw.ps
> 
> only after some postprocessing
> 
> $ ps2ps paw.ps paw1.ps
> $ lpr paw1.ps
> 
> the plot comes out correctly.
> 
> Is this a bug related to paw or to cups  ?

Not sure.  I will get in touch with upstream and ask.


> This problem somehow resembles a bit one of the paw package bugs
> 
> http://wwwasd.web.cern.ch/wwwasd/cgi-bin/listpawbugs.pl/120
> 
> of which I thought it had been fixed.

Well, when I try your PAW commands I end up with a postscript file that
includes the following lines (lines 88-92):

%%EndProlog
%%BeginSetup
newpath  gsave  20 28 t .25 .25 scale  gsave
%%EndSetup
%%Page: number 1

This matches the workaround described at the URL above.  I don't have
CUPS set up on any machines so I can't personally test what happens when
printing it - I have no trouble printing with regular BSD lpr on a
PostScript printer.  Can you verify that those lines also appear in the
postscript file PAW creates on your machine?  If so, my first guess is
that CUPS is ignoring the scale macro inside the BeginSetup ... EndSetup
section.

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
%%BeginPageSetup
newpath  gsave  20 28 t .25 .25 scale  gsave
%%EndPageSetup

and then run the result through lpr?

regards,

-- 
Kevin B. McCarty <[EMAIL PROTECTED]>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/    Princeton University
GPG: public key ID 4F83C751                 Princeton, NJ 08544


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to