Problem postscript files
Tim Writer
tim-s/rLXaiAEBtBDgjK7y7TUQ at public.gmane.org
Thu Jan 25 08:05:51 UTC 2007
Evan Leibovitch <evan-ieNeDk6JonTYtjvyW6yDsg at public.gmane.org> writes:
> When you say they won't print to postscript printers on a Linux server,
> that _might_ be because the Linux print systems are introducing their
> own garbage, so it's important to set your printing flags to ensure that
> extra file-processing is disabled. I've occasionally encountered
> situations in which the Linux print system, in a misguided attempt to be
> helpful, thinks the PS code is actually a source file, and prints the PS
> instructions rather than executing them!
>
> This means that, for instance, if you're using 'lpr' to print the file
> on a postscript printer under Linux make sure to use the "-l" flag.
Or, temporarily disable CUPS (or lpd) and copy the file directly to the
port. For example, for a parallel printer:
# cp file.ps /dev/lp0
--
tim writer <tim-s/rLXaiAEBtBDgjK7y7TUQ at public.gmane.org> starnix inc.
647.722.5301 toronto, ontario, canada
http://www.starnix.com professional linux services & products
--
The Toronto Linux Users Group. Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
More information about the Legacy
mailing list