Should ATS APIs used for Font.creatFont() be dropped ?

[Phil Race]

I just looked at
http://java.net/jira/browse/MACOSX_PORT-365
  GraphicsEnvironment.registerFont() returns 'false'

The basic reason for the failure is that the font is already
registered by createFont() .. so explicitly registering it
fails as already registered.

That's easy enough to fix for the PFB font but for a TTF font
there's the wrinkle that unlike the PFB font its being successfully
loaded via a native call to ATS. That also somehow causes the font to be
registered.

I suppose we could try to fight whatever makes that automatically
registered.

But I also think we'd need to make sure that fonts used in this way
but not registered are properly GC'd .. I am not sure if that is
happening right now.

But is the ATS code worth keeping? loadFileFont() only used for
Font.createFont()?

-phil.