🚀 go-pugleaf

In article <1h5d4qINN5vl@life.ai.mit.edu> petrilli@hal.gnu.ai.mit.edu (Chris  
Petrilli) writes:
> I have a couple NeXT machines at work and I've installed about 50 new
> typefaces on them, but unfortuately they seem not to be available across
> different applications and users.
> 
> For example, som, but not ALL of my typefaces are available in FrameMaker,
> but the rest are all available in Write Now (except for some that are marked
> "unusable" for some reason.)
> 
> Any ideas?  It's not permsissions, they are consistant across fonts.
> 
Hey Chris (and all the others ...),

where did you install the fonts? For make them usuable for all users they have  
to be installed at /LocalLibrary/Fonts. If the fonts are installed at the  
(User)/Library/Fonts directory only this user is able to work with these fonts.

'unusuable fonts' (in WN i.e.) are mostly caused by problems within the afm's:  
Check them to the originals: Are all lines represented (sometimes some lines at  
the CharMetrics are missing)? Or are some lines 'dubbeled' (sometimes a part of  
the afm file is repeated at the end)?

FrameMaker looks for fonts at /LocalLibrary/Fonts/afm (or  
(User)/Library/Fonts/afm). Does this directory exist? Are all afm's linked from  
the fontname.font to this directory? ... and if you have to do this now, it's  
better to create a directory /LocalLibrary/Fonts/outline too and link the  
outlines from fontname.font to this directory - there might be software which  
looks at this point for fonts ...

It might be easier to copy the afm's to /LocalLibrary/Fonts/afm, the outlines  
to /LocalLibrary/Fonts/outline, create /LocalLibrary/Fonts/bitmap and run  
'fontupdate_2.0' - this creates the fontname.font files and does the  
linking-job. Then run 'buildafmdir' as usual ...

-Borris-
-- 

---
Borris Balzer - Kennedyallee 34 - D-6000 Frankfurt am Main - Germany
Tel +49-69-639266 - Fax +49-69-6312324 - e-mail borris@boba.rhein-main.de