I haven't run across any issues with generating fonts under OS X, however Fontographer will not launch in the Classic environment of OS X unless you're using the non-FPU version of the application. There's more information in this tech note on the Macromedia site. Quite frankly, when I have to use Fontographer, I simply boot into OS 9 - it's much less painful.

I have an older Mac running OS9 that I use almost exclusively for Fontographer. My main Mac is running OSX, which I use for everything else.

As Grant said, it's possible to run FOG in OSX, but it's really not very happy there. It often quits unexpectedly when printing samples and working with character references. It also feels slow when it updates the drawing window. Changing to "Thousands of Colors" helps. I don't think there are any problems in generating fonts, though (no new ones, anyway).

When I finish the batch of fonts I'm working on, I'm ditching Fontographer as my main production tool and switching to FontLab. As Erik van Blokland told me at TypeCon, after you draw 600 or 700 characters in FontLab, you get used to it.

The major roadblock for FOG in Classic Mode on an OSX machine is that you cannot manipulate composite characters once they are created.

Make a U umlat with a direses over the top and try to move the direses with the mouse or the keyboard and it'll start spinning the old stopwatch till infinity. . . .

DONE!

For that reason alone I cannot use FOG on my X machine because I build out all of the composite glyhs. It's a damn shame - Jim Gallagher informed me that this is due to Classic mode referencing the Carbon Lib instead of the Bitmap file when you're creating any information that affects the bitmap/metrics information associated with the FOG file.

Oh well, I keep an 8.6 machine to do FOG work in for now and the X machine for Font Lab. I do expect to eventually abandon FOG once my brain makes the conversion. . .

Stuart :D