On Sun, Dec 30, 2001 at 03:44:59PM +0100, Jens Müller wrote:
| dman <[EMAIL PROTECTED]> writes:
| 
| > Say, in windows what did you specify the printer as?  I picked HP
| > Laserjet IIIp (the postscript version) so that windows generates
| > postscript and lets CUPS translate it to the printer's own protocol.
| > That could explain why I never ran into that issue -- I was sending
| > ps, not raw, data.
| 
| Do I have to set something for this on my Linux box? How does CUPS
| know it's PS?

It starts with "%!PS".  All PS files/streams/documents start that way.
If you look at /usr/share/misc/magic around line 5715 you can see the
logic to identify a postscript file.

| Well, I used raw format (DJ 840 C driver).

If it works for you :-).  The Canon I wanted to share with the windows
machines has no good drivers on windows thus I have windows send PS
and let cups filter it through ghostscript.  The other tradeoff is
upgrading or synchronizing changes in the configuration.  If all
machines send postscript, then they don't need to change and only one
machine is aware of the details of that printer.

-D

-- 

It took the computational power of three Commodore 64s to fly to the moon.
It takes at least a 486 to run Windows 95.
Something is wrong here.

Reply via email to