Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!eagle!news
From: edwill@venus.lerc.nasa.gov (Glenn L. Williams)
Newsgroups: comp.sys.apollo
Subject: Re: Postscript files
Message-ID: <1990Dec11.142001.4970@eagle.lerc.nasa.gov>
Date: 11 Dec 90 14:20:01 GMT
References: <9012051449.AA01247@cc2.cc.umr.edu>
Reply-To: edwill@venus.lerc.nasa.gov
Organization: NASA Lewis Research Center
Lines: 25
News-Software: VAX/VMS VNEWS 1.3-4

In article <9012051449.AA01247@cc2.cc.umr.edu>, obrennan@CC3.CC.UMR.EDU (obrennan) writes...
> 
>	When I try to print a Postscript file using the normal prf 
>	command , if I DON"T use the  -trans flag  it prints it as an
>	ascii file and simply prints the code for the PS file.  I also
>	thought that the 10.x (mine is 10.3) was supposed to recognize 
>	the type of file and print it as such but at least in my case
>	it doesn't.
> 
>The Postscript file, as per Adobe Postscript standard, MUST start with a %! as the
>first 2 characters in the file (usually %!PS-Adobe), otherwise the Apollo
>print filters will convert the text to postscript so that it comes out as
>Postscript of your Postscript text (i.e. sends your Postscript file as 
>Postscript text). Using the -trans option keeps it from applying filters.
> 

  We are running a DN3550 with Mentor Graphics 7.1 and 10.1 O.S.
Mentor's Postscript output contains two funnies that must be deleted
before our Postscript printers will work.  First, the very beginning
and very end of the files contain non-printing characters that *may*
confuse the printer.  Second, there is a line somewhere down in the file
with syntax  'letter 0 setjobtimeout'.  This line must be commented out
or removed, or the output will *not* work on the printer. I should mention
that we use 'offline' mode so we can send the output to various printers
on our lab network.