Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!neon.Stanford.EDU!pescadero.Stanford.EDU!philip
From: philip@pescadero.Stanford.EDU (Philip Machanick)
Newsgroups: comp.sys.mac.system
Subject: Re: System 7 and PostScript printing to file
Message-ID: <1991May31.164406.29017@neon.Stanford.EDU>
Date: 31 May 91 16:44:06 GMT
References: <3104@odin.cs.hw.ac.uk> <1991May31.020609.5174@vax5.cit.cornell.edu>
Sender: news@neon.Stanford.EDU (USENET News System)
Reply-To: philip@pescadero.stanford.edu
Distribution: comp
Organization: Stanford University
Lines: 23

In article <1991May31.020609.5174@vax5.cit.cornell.edu>, umh@vax5.cit.cornell.edu writes:
|> We've had lots of gripes about how large the new LaserPrinter print to file
|> files are and how life was so much better under 6.0.7. I'd just like to defend
|> Apple on this one by stating that I tried very hard using about 6 different
|> programs to patch the postscript at either the Mac or the UNIX end, and I only
|> once managed to get a 6.07 postcript disk file to print on our UNIX system. To
|> do that, I had to use som LaserWriter driver that was about six years old, and
|> some of my fancy fonts weren't printed properly.
|> 
|> The new scheme may eat up lots of temporary disk space and transfer time, but
|> it *works* and I for one thank Apple for it.

Right - but there's no harm in asking for improvements in the next
release. I would like some way of telling the driver what fonts it
can expect to find in the target printer, so it doesn't include them in
the generated PostScript.

My short term solution is to switch to a faster ftp program (I'm
trying XferIt 1.4, which seems much faster than MacIP) and to avoid
printing when the printer's in demand.
-- 
Philip Machanick
philip@pescadero.stanford.edu