A PC based ATM Adobe Type Manager may not directly recognize older
printer-only
Adobe PostScript fonts. This note shows one method to install these older
fonts.
Further support on https://www.tinaja.com
Consulting services available via don@tinaja.com
The problem:
I have a lot of older Adobe printer fonts on hand. Some on Apple II
hard drives, some on
a Mac, and many on hard drives for Laserwriter or QMS printers. These are
typically a
single text file consisting of an ASCII header, a hex-ASCII eexec section,
and an ASCII
trailer. If you translate these to a PC, they will often be ignored by
ATM.
One solution:
First, carefully read Adobe Tech Note
#7114 on ATM and Type I fonts. It turns out that
ATM demands either (A) a font in .PFB format and a .PFM metrics
file; or (B) A font in
.PFB format and a related .INF file and a related .AFM metrics file. All
in the same folder
having identical 8-3 DOS filenames. Such as CoBo____.PFB,
etc...
It appears that the Adobe Type-on-call disk only encrypts the
.PFB file. A cleartext but
hidden .PFM file is provided for all Adobe fonts. This is easily
copied or moved.
Here are detailed instructions:
(1) Review any license or use restrictions on the older Adobe PostScript printer font.
(2) Read the exact old font name using an editor or word processor.
(3) Get into Type on Call
and find the 8-3 PC filename for the exact same font. For instance
Courier-Bold
might be CoBo____.PFB. By beginning to order the font, you can find
out
in which numeric folder the needed font files are located. The .PFB files
are typically
found
in TOC /data/common/psfonts/041 or some similar numbered folder.
An
Adobe type catalog might be needed to find out that, say, Revue
is in the Aachen
numeric
file folder.
(4) Translate your
old printer font to the PC. Using comm utilities, Apple File Exchange,
or,
if all else fails, by uploading and downloading from a web site. Place
the file
in
a temporary work folder.
(5) Use Wordpad or
whatever to verify this is a clean textfile with an ASCII header,
a
hex-ASCII eexec section, and an ASCII trailer. Then rename the file as
the correct
8-3
DOS .PFA file. Such as CoBo____.PFA.
Make
certain the "true" DOS filename changes! You may have to
load into Word,
and
then "save as" using a full filename in quotes.
(6) Use my PFA2PFB.PS
to convert this .PFA file into a .PFB file in the same temporary
work
folder. Use Wordpad to verify this file has an ASCII header, a binary
eexec
section,
and an ASCII trailer. This filename should be similar to CoBo____.PFB
The length of the underline always must bring the total character count up to eight.
(7) Copy the matching
.PFM file from Type on Call to the temporary work folder.
Such
as CoBo____.PFM Be sure to get the (usually last) .PFM file! Use
right
mouse
properties to verify the hidden trailers.
UNHIDE THIS COPIED .PFM FILE! Again using right mouse properties.
(8) Since valid
.PFB and .PFM files are now in the same folder, the Install feature
of
ATM
should now recognize and install the font. Always use the exit button
on ATM,
instead of clicking out. Otherwise directory changes may not always
get reset.
(9) Check and verify the font prints normally by outputing a specimen page or whatever.
Note that older Adobe printer fonts will usually have newlines only,
rather than carriage
return and linefeed pairs. One way to view such a file is to bring it into
Netscape Gold, where
returns will present themselves on screen normally. A conversion to CR-LF
can be done by
loading into Netscape Gold, copying to the clipboard, and pasting to Notepad.
But .AFM files
are best left in their "newlines only" format.
Please report any problems to me.
Further support on https://www.tinaja.com
Consulting services available via don@tinaja.com