Path: utzoo!utgpu!attcan!uunet!pyrdc!netsys!lamc!well!brecher
From: brecher@well.UUCP (Steve Brecher)
Newsgroups: comp.sys.mac
Subject: Re: F/DAm 3.8 bug?
Message-ID: <7367@well.UUCP>
Date: 13 Oct 88 21:06:27 GMT
References: <72598@sun.uucp>
Reply-To: brecher@well.UUCP (Steve Brecher)
Organization: Software Supply, Sunnyvale, CA
Lines: 28


In article <72598@sun.uucp>, chuq@plaid.Sun.COM (Chuq Von Rospach) writes:
> I think this is a generic Font/DA Mover bug...
> Copy all of the files from [Adobe's] "Palatino Other" to Palatino Plain."
> ...take a look at "Palatino 12" -- it's trashed...

This is not a Font/DA Mover bug, but the result of structural defects
in Adobe screen font file resource maps that makes the files, in effect,
read-only. By copying fonts into the file, you were bitten.  The fact
that one particular font size was trashed was, in this context, coincidence.
I would suggest carefully checking all of the resources in your resulting
file after replacing the resource that was trashed -- there could be
others that were trashed or corrupted.

The workaround is to copy the contents of the files to new files by any
means that uses the Resource Manager to copy the resources -- e.g.,
copying with ResEdit -- before making any attempt to alter the
files.  Copying with Font/DA Mover would work from the standpoint of
getting an alterable file, but depending on how a typeface is split
up among files you could lose FOND references.

Adobe is aware of the defective resource map problem; it is caused by
bugs in the software they use to create the files (they do not use
the Resource Manager to construct the files).  Their newer Font Folio
screen font files do not split families into "plain" and "other", but
at least some of them still contain the resource map defects. Font Harmony,
a utility that comes with Suitcase II (of which I am author), will repair
defective Adobe screen font file resource maps.