info-mac@uw-beaver (12/10/84)
From: Michael Peirce <peirce@lll-crg.ARPA>
After exerimenting with the resource mover a bit, I've stumbled on to the
following useful item. You can move a Font into the resource fork of
any textfile so that even if the system doesn't have a copy of the font
handy, MacWrite will get it from the textfile itself. This means you can
send a file that uses a fancy or custom font in it to someone that does not
necessarily have that font. Normally you won't want to put a copy of the fonts
used by a specific document into it, but for special cases, like
storing a textfile on a central host, it works great.
You can also move a font right into MacWrite. This allows you to make
up special copys of MacWrite with special fonts built right in.
For information on how to mess with fonts and the resource mover see the
great documentation included with the fonts disks. (Thanks to the folks
who put that together!!!)
...Michael Peirce (PEIRCE@LLL-CRG)
P.S. You can also reverse this type of procedure to look at fonts that are
built into applications. The font in MacTerminal is rather interesting... info-mac@uw-beaver (12/13/84)
From: olson@harvard.ARPA (Eric Olson) Indeed, any application that loads resources from files (i.e., MacWrite, to get fonts) will look in the document resources, application resources, and system resources in that order, unless the programmer has selected otherwise. So, in general, you can count on being able to put resources in more specific places than the system file... and that includes fonts. -ERic.