home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!das-news.harvard.edu!husc-news.harvard.edu!humcr3.harvard.edu!veloso
- From: veloso@husc9.harvard.edu (Manuel Veloso)
- Newsgroups: comp.sys.mac.system
- Subject: Hacking a Font Folder Manager
- Message-ID: <1992Nov16.120555.17499@husc3.harvard.edu>
- Date: 16 Nov 92 17:05:54 GMT
- Article-I.D.: husc3.1992Nov16.120555.17499
- Distribution: world
- Organization: Harvard University
- Lines: 21
- Nntp-Posting-Host: humcr3.harvard.edu
- X-UserAgent: Nuntius v1.1.1d11
- X-XXMessage-ID: <A72D402210011817@humcr3.harvard.edu>
- X-XXDate: Mon, 16 Nov 92 17:10:10 GMT
-
- After looking at the Font Extension Manager, I figured that there had
- to be a better way. So I looked at the 'protypical' extension manager,
- "Extensions Manager 1.8", & found out that it's actually really easy
- to make it recognize the Fonts Folder.
-
- With Resedit:
-
- open the FTyp resource, go to the bottom of the resource, and type
- (don't type the quotes)
- 'fontfonD'
-
- then go to the fld# resource, and add
- fonD
- Fonts (disabled)
-
- if you like, you can delete all the other FTyp's and fld#'s, leaving
- just the above changes.
-
- Then, configure EM to recognize 'LWFN', 'ffil', and 'FFIL'. Voila! you've
- got a font manager that not only does sets, but is a cdev & can be
- used @startup. How 'bout that?
-