Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!zephyr.ens.tek.com!tekig5!briand
From: briand@tekig5.PEN.TEK.COM (Brian D Diehm)
Newsgroups: comp.sys.mac
Subject: Re: NFNT family names...clarification...
Message-ID: <5455@tekig5.PEN.TEK.COM>
Date: 24 Jan 90 20:13:12 GMT
References: <1990Jan24.001341.3232@athena.mit.edu> <38059@apple.Apple.COM>
Reply-To: briand@tekig5.PEN.TEK.COM (Brian D Diehm)
Distribution: usa
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 32

In article <38059@apple.Apple.COM> chuq@Apple.COM (Chuq Von Rospach) writes:

>Finally, select the FONT resource, then do an "open general" from the File
>menu of Resedit. If you just double-click, it won't show you the zero point
>FONT resources, which is what you need to modify.

>use "Get Info" on each of the zero point FONT resources, making sure the
>name you use is the same as the name in the FOND.

>Clsoe and save. Do this on a COPY. Inspect it with Suitcase (or whatever)
>and it should now only have the new names.

Chuq is mostly correct here, but zero-length FONTs are only included with
FONT families, ***NOT*** NFNT families. You SHOULD NOT create a zero-length
FONT resource for NFNT resource families.

If your FOND resources point to FONTs, then you should have a zero-length FONT
resource as well. This resource isn't really needed or used by newer systems;
it is only to provide compatibility with VERY old systems that didn't have FOND
resources. Pre-1986 or so. However, the Font/DA Mover will complain if it
doesn't find the zero-length FONT, but only when you try to remove a complete
set of FONTs (say, all the New York).

So, Apple, why should the Font/DA Mover complain at this point, and why should
it leave orphaned FONT resources around? Seems unnecessary and unfriendly,
Apple. I'd call it a bug.

-- 
-Brian Diehm
Tektronix, Inc.                (503) 627-3437         briand@tekig5.PEN.TEK.COM
P.O. Box 500, M/S 39-383
Beaverton, OR   97077                        (SDA - Standard Disclaimers Apply)