🚀 go-pugleaf

In article <4082@hydra.gatech.EDU> gt0818a@prism.gatech.EDU (Paul E. Robichaux) writes:
>Since my poor little Plus doesn't have a printer, I've gotten in the habit
>of printing PostScript to disk, then uploading the PS to one of our unix
>boxes and using macps to print it.
>Last week, my copy of ATM and the Plus Pack (thanks, MacConnection!) got here,
>and now I notice that my PostScript files are *huge*, i.e. an expansion
>in some cases from 30-40k to 340-390k.
>Is this because ATM is including the outline fonts from the system folder?
>Is there any way to suppress this? Should I just say "to hell with it" and
>buy a DeskWriter?

The files do have a copy of the fonts used in your document. Unfortunately with
the current ATM there is no way to disable this. Since the font request is 
from the print driver, ATM is just supplying what is asked for. If ATM were
to disable itself from doing this, it would have to be a manual process and
could cause problems, i.e. you have font downloading turned off, now are 
connected to a LaserWriter, the font isn't there, and ATM won't supply it.
While the pros and cons of the issue are discussed by the ATM programmers, a
"hack" solution was given to me by one of our users and I'll pass it on.

ATM locates the outlines it will download by name, but the LaserWriter driver
looks for name and file type 'LWFN'. The user found out that by changing the
type to something different, like 'xWFN', the LaserWriter driver wouldn't
think the font was available, thus it wouldn't ask for it, and the spool file
created wouldn't have the font included. His fix was so the font wasn't 
sent to the spooler, it should be the same solution so it won't be sent to
the PostScript disk file.
  The above instructions are my translation of what a user told me worked for 
him. I haven't tested it, nor has Adobe, and so I won't vouch for it working 
- this info is posted only for information and possibly helpful purposes.

Hope the above info does work and help users having the previously mentioned
problems.

-- 
Brian Bezanson                                          bezanson@adobe.com
Adobe Systems Incorporated           The opinions expressed above are my
                                     own and may not represent those of Adobe.