Font resources moved into OTHER files

Info-Mac discussion from 1984 - 2002.
Locked
User avatar
Info-Mac
Administrator
Posts:13716
Joined:December 21st, 1988, 11:00 am
Font resources moved into OTHER files

Post by Info-Mac » January 11th, 1985, 2:07 am

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver
Newsgroups: fa.info-mac
Subject: Font resources moved into OTHER files
Message-ID:
Date: Sun, 9-Dec-84 23:58:51 EST
Article-I.D.: uw-beave.146
Posted: Sun Dec 9 23:58:51 1984
Date-Received: Tue, 11-Dec-84 03:26:13 EST
Sender: daemon@uw-beaver
Organization: U of Washington Computer Science
Lines: 22

From: Michael Peirce

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...
Locked