🚀 go-pugleaf

There have been numerous posts about font installation, most centering on the  
old afm, bitmap, and outline directories.  I've been having some problems with  
Frame 3.01 and thought you might find the following email from Frame  
interesting.  I haven't gone back to the old style directories, though...


> Date: Wed, 16 Dec 92 14:37:47 PST From: ngt@frame.com
> (Nancy Taylor) To: steved@bullwinkle.bankone.com
> Subject: FM 3.01 for NeXT Cc: ngt@frame.com
> 
> Steve,
> 
> Font Problems We use more font information than other
> applications. We rely on more font resources than other
> applications
> 
> The NeXT does not have the same fonts as other platforms.
> The fonts are provided by NeXT All versions of FrameMaker
> should support Adobe Type 1 PostScript fonts and are not
> stored in FrameMaker. Example Bookman.This is a
> limitation from the NeXT Co. The fonts must be kept in the
> NeXT library not in your home directory or this will hang
> up or crash the system. For networking put them in a local
> library.
> NeXT/Arachnid/3.0.1/FrameMaker.app/fminit.20/fontdir
> he "new" style of font installation only requires that
> the font directory contain an afm file (e.g.,
> Courier-Bold.font/Courier-Bold.afm); it doesn't
> require the presence of afm/Courier-Bold.afm,
> although all NeXT-supplied fonts have them for backward
> compatibility. However, fonts from outside vendors
> typically don't have the afm/*.afm files, and
> FrameMaker has been having trouble with these. To fix:
> make sure that each font has an afm/<fontname>.afm file
> symbolically linked to its
> <fontname>.font/<fontname>.afm. . I hope this
> information will be of help.
> 
> Best Regards,
> 
> Nancy Taylor Frame Technical Support 
> 

Steve
-- 
Steve Dieringer NeXTMail:  steved@bankone.com
     (formerly steved@essex.com)