[comp.sys.mac] Font/DA Mover 3.4 & Princeton Font

jdm@ut-ngp.UUCP (06/05/87)

	My experience with Font/DA Mover versions 3.4 and 3.5 is that
they don't recognize the Princeton Font (e.g. Princeton doesn't appear in 
the list of Fonts even though it's in the system or Font file opened!). Version 
3.2 worked just fine. As far as I can tell this font has a FOND resource 
that is perfectly okay, and the appropriate FONT resources, and of course 
it works fine in MacWrite and Word, etc.
	Anybody know whats up? Is Apple trying to tell us to give up
using this font :-}?
						Jim Meiss
						jdm@ut-ngp.UTEXAS.EDU

mjsamorodny@thunder.UUCP (06/11/87)

In article <5337@ut-ngp.UUCP> jdm@ut-ngp.UUCP writes:
>
>	My experience with Font/DA Mover versions 3.4 and 3.5 is that
>they don't recognize the Princeton Font (e.g. Princeton doesn't appear in 
>the list of Fonts even though it's in the system or Font file opened!). Version 
>3.2 worked just fine. As far as I can tell this font has a FOND resource 
>that is perfectly okay, and the appropriate FONT resources, and of course 
>it works fine in MacWrite and Word, etc.

	I have had the same problem trying to install Princeton font,
(version 1.4 I believe, is there a later one?).  The problem is quite
simple--Princeton's font ID number is 13 which happens to also be the
font ID of an Apple Laserwriter Plus font (Zapf Chancery I think).
	
	Why this causes the Princeton font not to appear in the Font/DA
mover window I don't know, but if you hack into the suitcase file with
ResEdit you find an interesting thing.  The new FOND ID number is 13
and the name shows up in ResEdit as Zapf Chancery when I open the FOND
resource.  But when I open the FONT resource, the name is still Princeton.
Removing Zapf Chancery from my system file made no difference.
The key seems to be to renumber the FOND ID number so it doesn't conflict,
but I haven't figured out how to do this.  Do the FONT ID's also have to
be changed?

	It seems to me that Apple reserved some of the lower ID numbers
way back and now we see the result of creating a new font in the
reserved range.  Still, this should be an easy fix for someone more
familiar with resedit.

					- Sonny