Article View: comp.sys.next.sysadmin
Article #354Re: Unusable fonts
From: Glenn Reid
Date: Sun, 02 Aug 1992 00:55
Date: Sun, 02 Aug 1992 00:55
21 lines
1277 bytes
1277 bytes
Ray Ghanbari writes > Does anyone have a good idea how unusable font come about? NeXTanswers > PostScript.746 is less that illuminating. > > On one of our systems, the Symbol font has recently become <<Unusable>> > when brought up in a font panel. The most common cause of this is that the AFM file cannot be parsed for whatever reason. Since the file is one of the system fonts (Symbol), either the permissions changed somehow or the file got corrupted. I'd recommend copying Symbol.font from another machine and making sure all the preferences are set identically to the other fonts, then proceeding with the rest of the NeXTanswers steps of removing .afmcache, .font*, and running "buildafmdir" (or whatever it is that they suggest). -- Glenn Reid NeXTmail: glenn@rightbrain.com RightBrain Software 415-326-2974 (NeXTfax 326-2977) Palo Alto, California
Technical Details
Message-ID:
<803@rtbrain.rightbrain.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!nntp1.radiomail.net!fernwood!rtbrain!rightbrain.comReferences:
<1992Jul31.212549.1899@athena.mit.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!nntp1.radiomail.net!fernwood!rtbrain!rightbrain.com From: glenn@rightbrain.com (Glenn Reid) Newsgroups: comp.sys.next.sysadmin Subject: Re: Unusable fonts Message-ID: <803@rtbrain.rightbrain.com> Date: 2 Aug 92 00:55:45 GMT References: <1992Jul31.212549.1899@athena.mit.edu> Sender: glenn@rightbrain.com Reply-To: glenn@rightbrain.com Lines: 21