Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!pepe!shane
From: shane@pepe.cc.umich.edu (Shane Looker)
Newsgroups: comp.sys.mac
Subject: Re: Document fonts: I thought this would work -- why not?
Message-ID: <515@mailrus.cc.umich.edu>
Date: 18 May 88 13:52:11 GMT
References: <394@kosman.UUCP>
Sender: usenet@mailrus.cc.umich.edu
Reply-To: shane@pepe.cc.umich.edu (Shane Looker)
Organization: University of Michigan Computing Center, Ann Arbor
Lines: 31

In article <394@kosman.UUCP> kevin@kosman.UUCP (Kevin O'Gorman) writes:
>It seems to me this trick used to work: what has happened?
>
>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.
>
>I tried it in MacWrite, and Word, and no such luck.  I thought I remembered
>that this worked because the system sees the resources of all open files.
>Shouldn't this work?  It sure seems like a good idea for seldom-used
>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.

During the initialization phase of the program, all fonts (in MacWrite)
are loaded with a call to AddResMenu (I think, don't have IM here right now).
(Word does essentially the same thing, but plays around some more.)

As a result, the Font menu list is installed *before* your document is
even opened.  (It is just a parameter to the program after all.)  So
when the Font menu is built, it does have all the known fonts put into it.

A little extra code could make the font menu add document fonts, but the
code is trickier to make the fonts dissappear when the document is closed.


Shane Looker
shane@pepe.cc.umich.edu 
uunet!umix!pepe.cc.umich.edu!shane
Looker@um.cc.umich.edu