Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!princeton!phoenix!lardieri
From: lardieri@phoenix.Princeton.EDU (Stephen P Lardieri)
Newsgroups: comp.fonts
Subject: Re: Adobe Type Manager and postscript files
Keywords: ATM, postscript
Message-ID: <9287@idunno.Princeton.EDU>
Date: 8 May 91 19:13:13 GMT
References: <1991May8.185123.6001@cs.yale.edu>
Sender: news@idunno.Princeton.EDU
Followup-To: comp.fonts
Distribution: usa
Organization: Princeton University
Lines: 19

Before printing a file, the laserwriter driver checks to see if any fonts
need to be downloaded.  Normally, it asks the attached laserwriter for a
font directory, and then compares this to the fonts requested in the file
it is printing.  If it finds a font in the file that isn't already in the
laser printer, it looks for it in the System Folder and the application's
folder.  If it can't find a PostScript font there, it creates a bitmap equal
to (about) 4 times the size needed, and downloads that instead.

Since there is no laser printer attached to your machine, the laserwriter
driver thinks there are no fonts already resident in the printer it is
"printing" to, so it tries to download EVERY font used in the document.
Naturally, all those fonts are present in the System Folder; you installed
them there when you were installing ATM.  So they all get included in the
PostScript file you are making with cmd-F.

The only way around this that I know of is to rename the PostScript fonts
in the System Folder before trying to print.  Turning off ATM will do nothing,
since it isn't ATM's fault that the fonts' postscript code is getting
included in the first place; it's the LaserWriter driver's fault.