🚀 go-pugleaf

In article <1993Jan8.125232.5777@Informatik.TU-Muenchen.DE> rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel) writes:
>A bit off topic (but more related to this group), wouldn't it be better
>to integrate a PostScript to <whatever printer> converter into a queue
>processor and use it with the normal PSCRIPT driver? Isn't the queue
>processor the part which gets the PS from the spool file (the PSCRIPT
>driver puts it there) and sends it to the port?

Kai, I was thinking the very same thing.  It would certainly be a heck
of a lot easier, wouldn't it?

(In a nutshell, you'd drop in the GhostScript code, put the queue
processor wrapper around it, and let it act as an intermediary between
the applications which are doing the printing and the device-specific
print drivers.)

You could also do it as a device monitor (a la LPRMON in TCP/IP), but
I don't recommend it.

Correct me if I'm wrong, but I think the queue processor programming
is rather straightforward and well documented, no?  Or am I missing
something?

I obviously hope this matter can be resolved to everyone's
satisfaction, and that such incidents occur rarely, if at all, in the
future.

-- 
Timothy F. Sipples      | Read the OS/2 FAQ List 2.0h, available from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
Dept. of Econ., Univ.   | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637       | [Read the List, THEN post to ONE OS/2 newsgroup.]