🚀 go-pugleaf

In article <11750@well.UUCP> brecher@well.UUCP (Steve Brecher) writes:

>In article <9264@polya.Stanford.EDU>, kaufman@polya.Stanford.EDU
>(Marc T. Kaufman) writes:

-> Suitcase [II] is randomly renumbering the FOND resources to avoid
-> conflicts.

>Suitcase II does not renumber FONDs.  A utility which is part of the
>Suitcase II product, Font Harmony, may in some cases renumber FONDs in
>suitcase files which the user chooses to process.  The original poster did
>not mention using Font Harmony.  In fact, not using it (i.e., having font
>number conflicts) may have been part of his problem.

Yes, of course.  I used Font Harmony when making up the suitcases.

>(Font Harmony's renumbering is not random.)
?? It sure seems isomorphic to random.  It is not RANDOM only in the sense
that it insures non-conflict with other FOND ids.

-> You can recover your old font numbers ... by using ResEdit to change the
-> resource numbers of the FOND resources back to the simple numbers used
-> before. ... It is not necessary to change FONT or NFNT numbers.

>If a FOND is renumbered via ResEdit, it is also necessary to change the
>family ID number inside the FOND, to renumber any associated FONTs, and to
>change the FONT entries in the FOND's association table.

I didn't renumber the family ID or the FONTs, since Font Harmony changed
everything to NFNTs, which certainly don't need to be renumbered.

Marc Kaufman (kaufman@polya.stanford.edu)