Article View: comp.sys.next.misc
Article #3141Re: More Font installation troubles
From: Allen B
Date: Thu, 05 Nov 1992 18:56
Date: Thu, 05 Nov 1992 18:56
16 lines
1110 bytes
1110 bytes
In article <1992Nov5.020444.24718@leland.Stanford.EDU> spagiola@frinext.stanford.edu (Stefano Pagiola) writes: > As root, I placed them in /LocalApps/Fonts, then ran buildafmdir and > cacheAFMData on that directory. All the fonts appeared in the font > panel and seemed to work (ie would preview) when I tried as root. > > After logging out and then back in as a regular user, all the fonts > were still in the font panel, but most (not all) were marked > unusable. Yes, by default, I've noticed, the permissions on the files created by buildafmdir are wrong. chmod 644 all the '.' files in your font directories and see if that works. It did for me. ab
Technical Details
Message-ID:
<Bx9B9n.9Ly@mentor.cc.purdue.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!destroyer!gatech!purdue!mentor.cc.purdue.edu!newsReferences:
<1992Nov5.020444.24718@leland.Stanford.EDU>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.misc Path: arc1-ca.pugleaf.net!sparky!uunet!destroyer!gatech!purdue!mentor.cc.purdue.edu!news From: ab@nova.cc.purdue.edu (Allen B) Subject: Re: More Font installation troubles Message-ID: <Bx9B9n.9Ly@mentor.cc.purdue.edu> Sender: news@mentor.cc.purdue.edu (USENET News) Organization: Purdue University References: <1992Nov5.020444.24718@leland.Stanford.EDU> Date: Thu, 5 Nov 1992 18:56:10 GMT Lines: 16