Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!think!yale!cmcl2!esquire!baumgart
From: baumgart@esquire.dpw.com (Steve Baumgarten)
Newsgroups: comp.sys.mac
Subject: Re: ATM
Message-ID: <1760@esquire.UUCP>
Date: 31 Jan 90 22:41:57 GMT
References: <1484@mit-amt.MEDIA.MIT.EDU> <780105@hpvcfs1.HP.COM> <1689@adobe.UUCP>
Sender: news@esquire.UUCP
Reply-To: baumgart@esquire.dpw.com (Steve Baumgarten)
Organization: Davis Polk & Wardwell
Lines: 28
In-reply-to: gelphman@adobe.COM (David Gelphman)

In article <1689@adobe.UUCP>, gelphman@adobe (David Gelphman) writes:
>    Today Adobe Systems announced that a new improved version of Adobe Type
>Manager is available. It will be made available as an upgrade to the
>existing version for current owners of ATM. Version 1.2 allows Bitstream
>Type 1 fonts to work with ATM.  [ ... ]

>    Other improvements in version 1.2 include better character spacing
>when printing from applications which do not support fractional character
>width spacing, bold characters at small point sizes can be more easily
>distinguished from plain type, performance is improved at larger point sizes,
>and a program for printing banners on the ImageWriter printer is included.

Does it also fix the problem of forcing fonts to be downloaded when
you save a print job to a PostScript file via cmd-F or cmd-K?

Someone had mentioned that a good workaround was to change the file
types of the printer font files from LWFN to xWFN, but this breaks
TypeAlign, which seems to look for files of that type.

It would be best, of course, if Adobe would allow us to put font files
in a special folder that is otherwise ignored by the system.  Do any
of you guys at Adobe know whether this is being considered?

--
   Steve Baumgarten             | "New York... when civilization falls apart,
   Davis Polk & Wardwell        |  remember, we were way ahead of you."
   baumgart@esquire.dpw.com     | 
   cmcl2!esquire!baumgart       |                           - David Letterman