Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!rpi!uupsi!sunic!ugle.unit.no!eik.ii.uib.no!usenet
From: robmack@ii.uib.no (Robert MacKinnon )
Newsgroups: comp.lang.postscript
Subject: Re: How can I tell if a file is "postscript"
Message-ID: <1991Mar14.075725.6766@eik.ii.uib.no>
Date: 14 Mar 91 07:57:25 GMT
References: <1448@vidiot.UUCP> <449@heaven.woodside.ca.us> <1460@vidiot.UUCP> <Qbr2bdK00VQs40k49S@andrew.cmu.edu> <1991Mar13.160331.25024@maths.nott.ac.uk>
Organization: Institutt for Informatikk, UiB, Bergen, Norge
Lines: 20

In article <1991Mar13.160331.25024@maths.nott.ac.uk> anw@maths.nott.ac.uk (Dr A. N. Walker) writes:
>	I don't know if there's a complete answer.  Here, we simply
>shovel whatever comes to the LW spooler direct to the LW, and it's
>hard cheddar if it isn't PS (at least it usually fails quickly).
>If people want listings, they have to call an ASCII -> PS program.

We're running IBM RISC System/6000's here at BSC.  They have the ability to
define 'virtual' printers.  The solution for us is to define two virtual
printer queues each for our LW and QMS printers.  One queue, ps<whatever>, will
take PostScript, interpret it and printout the graphic.  The other queue,
lp<whatever>, will take any input, call pstext from TranScript and print
the input as a text stream.  If a user were to submit PostScript to ps1
for instance, the PostScript would be interpreted and their graphic image
would result.  If they submit the same PostScript to lp1, a listing of
the PostScript code results.  The effect of the virtual queues is consistent
and predictable.  The users seem to like it as well.
>
Robert MacKinnon
Bergen Scientific Centre
Bergen Norway.