[Wylug-help] Problem printing postscript file

Gary Stainburn gary.stainburn at ringways.co.uk
Fri, 7 Feb 2003 09:17:38 +0000


On Thursday 06 Feb 2003 3:59 pm, Frank Shute wrote:
> On Wed, Feb 05, 2003 at 02:05:11PM +0000, Gary Stainburn wrote:
> > Hi Nik,
> >
> > My printer system is installed fine and I can print other postscript
> > documents and documents from apps like Openoffice with no problems.
> >
> > It appears to be just this one document that the printing system doesn't
> > like.
> >
> > Gary
>
> I'm afraid I'm away from my postscript printer ATM but it sounds like
> if you haven't got a ps printer it could be that ghostscript is
> failing to convert it properly to whatever language your printer
> understands.
>
> You could try running ghostscript from the command line on the file
> and then cat the file to /dev/lpr or whatever it is. Something like:
>
> $ gs -sPAPERSIZE=a4 -sDEVICE=ljet3 -dNOPAUSE -sOutputFile=foo.pcl foo.ps
> $ cat foo.pcl > /dev/lpr

Hi Frank,

I tried this and it printed fine - with no errors or warnings from gs.  It's
funny tho' that I can simply 'lpr gradient2.pdf' and the filter works fine,
but if I 'lpr gradient2.ps' I simply get an empty page. I created the pdf
using ps2pdf which is simply a wrapper for gs.

Spooky eh?

Anyway, as it's a PDF I want anyway so I can put it on my web site, it's a bit
academic.

Thanks anyway

Gary

>
> If that works then the problem is with your filter.
>
> My printing hassles died as soon as I invested in a cheap PS printer
> & wrote my own filter:
>
> #!/bin/sh
>
> cat -
> echo "\n"
>
> Anything that needs converting to PS first I do by hand.

--
Gary Stainburn

This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000