Path: utzoo!attcan!uunet!husc6!bbn!bbn.com!levin
From: levin@bbn.com (Joel B Levin)
Newsgroups: comp.sys.mac
Subject: Re: Document fonts: I thought this would work -- why not?
Message-ID: <24711@bbn.COM>
Date: 18 May 88 17:00:39 GMT
References: <394@kosman.UUCP> <515@mailrus.cc.umich.edu>
Sender: news@bbn.COM
Reply-To: levin@BBN.COM (Joel B Levin)
Organization: BBN Communications Corporation
Lines: 28

In article <515@mailrus.cc.umich.edu> shane@pepe.cc.umich.edu (Shane Looker) writes:
(In article <394@kosman.UUCP> kevin@kosman.UUCP (Kevin O'Gorman) writes:
(>I thought that I could option-open a document in Font/DA mover, and put
(>a font in the resource fork for that document, and have it used just by
(>that document.
(>display fonts and the like.
(
(It is a good idea, but... it doesn't work.  The reason that it doesn't
(work is because of the way fonts are installed when the program is run.
( ...

Another poster mentioned an alternate solution, which is useful when
you want to have some particular font available whenever you run (say)
MacWrite, but don't need it for other applications: place the font in
MacWrite itself (using option-open in F/DA mover).  This works, well,
almost.  If two fonts in two different resource files (e.g., System
and MacWrite) use the same font number, they will get confused in
mysterious ways when you try to use these fonts.  The only two
solutions for this I know of involve having the font around all the
time: put all fonts in the System file, or put them all in a single
font file and use Suitcase or F/DA Juggler (I presume) to make them
available.  (This works because F/DA mover can resolve conflicting
font numbers.)  Neither of these solutions helps your problem.

	/JBL
UUCP: {backbone}!bbn!levin     USPS: BBN Communications Corporation
ARPA: levin@bbn.com                  50 Moulton Street
POTS: (617) 873-3463                 Cambridge, MA  02238