Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!mailrus!cwjcc!gatech!ncsuvx!ccvr1!garvin
From: garvin@ccvr1.uucp (Michael A. Garvin)
Newsgroups: comp.sys.amiga
Subject: Re: VLT version 4.058
Message-ID: <3664@ncsuvx.ncsu.edu>
Date: 15 Aug 89 15:13:29 GMT
References: <1989Aug14.220122.561@utstat.uucp> <20020@swrinde.nde.swri.edu>
Sender: news@ncsuvx.ncsu.edu
Reply-To: garvin@ccvr1.ncsu.edu (Michael A. Garvin)
Organization: Bill 'n Opus Campaign HQ
Lines: 55

In article <20020@swrinde.nde.swri.edu> kent@swrinde.UUCP (Kent D. Polk) writes:
>In article <1989Aug14.220122.561@utstat.uucp> davids@utstat.uucp (David Scollnik) writes:
>[...]
>
>(Info about VLT's image save to postscript file option}
>
>>HOWEVER ... the laser printer I have access to seems unable to 
>>process these files, although it will print postscript files 
>>generated on the Sun Workstations used alongside the Amiga  
>[...]
>
>Interesting... I posted a message a while back about getting
>postscript output from the Amiga to a Sun postscript printer. I am
>currently using ProWrite/ProScript still since the other options
>suggested don't work. For example, Ifftops generates garbage on the
>postscript printer. I'm just sending the file to the Sun & then:
>lpr 'file.ps'. What's wrong?
>
>kent@swrinde.nde.swri.edu

     Well, first about VLT.  I had to change the PostScript header sent out
with it to work with the Apple LaserWriter.  Turns out that they don't like
the definition that VLT uses for showing a line on the page.  The offender
is (in S:TekProlog.PS):

/s  {stroke newpath show}  bdef

     Taking this out causes problems, though.  You have to edit the VLT
output PostScript file and take out all the references to this bdef.  The
easiest way I've found to do it is to do a global search and replace on ")
s" and replace with ") show".

     Now, onto the PostScript printing problem.  This depends on how you're
getting the output to your PostScript printer, but we had a similar problem
using a filter called "ln03rof" (it turns ASCII into PostScript for the
PostScript capable DEC LN03 laser printer).  We would get our PostScript
printed out nicely for us; not the page set up by the PostScript code but
the code itself (a source listing and not the final result).  It turns out
that the filter was wrapping the PostScript code in its own PostScript
header; the result being that our code was being treated as text since the
filter's PostScript was being interpreted first.  Our fix was to read the
documentation (gasp!) and learn that we needed a line in our call to the
filter to tell it that the text going through it may be PostScript and not
to wrap it.
     Other possible problems: CR/LF getting screwed up during transfer from
Amiga to printing machine, not using ASCII file transfer method (Kermit
binary instead of Kermit ASCII), or the filter not liking the Amiga code for
some arcane reason.  This is, of course, assuming that you're using a filter
program and not sending the file straight to the printer.

     Anyways, hope this helps.

garvin@ccvr1.ncsu.edu
Michael Garvin
NCSU Computing Center, Raleigh, NC