Issues with FontReserve and FreeHand MX Mac?

This information was provided to me through a 3rd party. Seems like it touches
on your issues. Hope it helps.

OSX Panther Font Book Overview
The main problem we found is that OSX does not handle fonts the same as
Classic. This was not as much of
an issue until OSX Panther introduced Font Book. Although this seems like a
font managing solution, it is
unable to handle font additions, removals, activations and deactivations as
well as a 3rd party extension. In
reality Font Book is not much more than an interface for adding and managing
fonts in your system. Much
like dropping fonts directly into your system folder in OS 9. The result then
was usually corrupt fonts and system
crashes. The same happens when using Font Book. Using Font Book might only be
effective if you do not
run any 3rd party font software and are not adding or deleting fonts on a
regular basis. The best solution is not
to use Font Book at all.

Font Issues
After upgrading all of our Macs to OSX Panther we proceeded to update to the
newest versions of our graphics
software. This includes particularly Extensis Suitcase X1, Quark Xpress 6, and
Adobe CS. First problem
encountered was when loading fonts into Extensis Suitcase. Fonts would not
appear inside of Extensis
Suitcase after loading. The solution we came up was to load the fonts into
Font Book. The fonts were visible
and loaded without a problem. This situation occurred a few more times and
Font Book still seemed to be a
good alternative until applications begin to crash. First to go was Safari and
any help or software install that
uses internet resources. It turns out that OSX supplied applications like
Safari, Address Book, Mail etc. rely
on certain fonts, like Helvetica and Helvetica Neue Datafork. Usually problems
arise from conflicting, corrupt
or missing fonts. This becomes more complicated since OSX now supports the
following font formats with
these extensions.

? TrueType fonts (with the extension .ttf)
? TrueType collections (with the extension .ttc)
? OpenType fonts (with the extension .otf)

Fixes for OSX Panther Font Book Issues
Since we had been using both Font Book and Extensis Suitcase, font conflicts
began to occur. Any time a font
is added to Extensis Suitcase, ( for example a version of Helvetica) a
conflict error would pop up. Even when
disabling fonts in Font Book, the conflicts continued. We found that whenever
a font is loaded into Font Book,
it copies the fonts to several locations inside your system. Disabling and
deleting these fonts from the system
seems to be the only solution. It is not recommended that you delete Font Book
all together because it is a
resource for OSX supplied software. If fonts have not been added to Font Book,
then the problem is probably
in the 3rd party font software. Troubleshoot here before deleting fonts or
files from Font Book and the system.
Isolating and deleting from 3rd party font software is easy and straight
forward. To delete fonts from Font
Book and the system, go to the hard drive and open the Library folder. Here
there is a folder named fonts.
Delete only the fonts that have been added and not fonts that came with Font
Book. In the hard drive also go
to users, library and fonts. Repeat the same deletions here. If more than one
user, do the same to the other
users. Also inside the hard drive, go to system and then to fonts. Repeat the
same steps here and if multiple
users do the same for those users. In short, you need to delete conflicting
fonts form the Library, Users and
System folders. It is recommended that before deleting the fonts, copy them to
your desktop in case a OSX
font is moved by accident. If this happens, you will have to reload those
fonts from the system disks.

DO NOT DELETE THESE FONTS
?Geneva
?Keyboard
?LastResort
?LucidaGrande
?Monaco
?Helvetica
?Helvetica Neue
?Monaco
Classics System fonts:
?Charcoal
?Chicago
?Geneva
?Monaco

There are also font cache related problems. The font cache issue can be
cleared up by running font cache
cleaning software like ?Font Cache Cleaner.? Note that you must close all
other applications before cleaning
caches. Also reboot your computer immediately after cleaning caches. It is
also possible to manually clean
font cashes by doing a search for the cache folders on your hard drive. The
problem with this is that some
applications by Adobe and Microsoft use font caches. If one of these font
caches is removed, you may cause
some damage to the apps and might have to re-install.

About Font Book and Corrupt Fonts
After deleting and disabling all the fonts used in Font Book, make sure to
delete them once all the conflicts are
solved. Do not copy those fonts to a 3rd party font software since they most
likely are corrupt. Although OSX
Panther now handles more font formats, Font Book corrupts any set created
which has mixed font formats, rendering
them useless. It seems that if different font formats are in one set, Font
Book does not know how to
handle their differences.

Classic Fonts in OSX Panther
There have been instances where fonts used in Classic and Classic
applications, do not load or work in OSX.
This is one issue which is still up in the air. Since we deal with multiple
clients and have to adapt to whatever
file formats are thrown our way, we find that working these files containing
Classic fonts only work in Classic.
Unfortunately this has been the only work around which is far from a solution
for OSX. It seems that these are
just transitional issues which will hopefully work themselves out once
everyone is working in OSX.