🚀 go-pugleaf

Actually, I think this is a generic Font/DA Mover bug, but I'm not thrilled
to see it happen under 6.0.2, so I thought I'd pass it along. Have other
people seen this?

I'm installing 6.0.2. It's currently a virgin maching, running under Finder.
Take two related font files, for instance Palatino Plain and Palatino Other.
These two files contain the normal style bitmaps for the Palatino Font and
all the special bitmaps (B Palatino, I Palatino and BI Palatino).

Open up both Font files with F/DAM. Copy all of the files from "Palatino
Other" to Palatino Plain." Before you do, keep a copy of "Palatino Plain"
because you'll need it.

Once everything is copied, take a look at "Palatino 12" -- it's trashed,
about 4000 bytes instead of 7000. So open up your saved copy of "Palatino
12" and copy a fresh version across. Bingo. A working Font file all set to
turn into an NFNT or something similar.

You have to copy the "other" fonts 'on top' of the Plain fonts. Note that
you're not actually touching the plain font -- the act of copying in the
related 12 point fonts trashes the plain 12 point font. Copying the plain
fonts into the "other" file doesn't seem to damage anything. The only font
that gets damaged is the 12 point plain, and it seems to get hit every time.

Anyone else see this? Can anyone follow those steps and *not* reproduce it?
I'm using literally virgin floppies, have just reformatted my disk and used
the standard installer script, no INIT's, no *nothing* so I can't see how
it's something I'm doing, but you never know...




Chuq Von Rospach			chuq@sun.COM		Delphi: CHUQ
Editor/Publisher, OtherRealms