How to use TeX Gyre fonts installed by TeX Live

Toggling LCD font smoothing (subpixel rendering) should have an immediate effect on the System Preferences window with most displays.

LCD font smoothing is not enabled automatically on some LCD displays though. You might be able to force them to use it with defaults write -g AppleFontSmoothing -int 2, which corresponds to the pre-10.6 medium setting or enabling LCD font smoothing on most displays.

10.5 used to allow choosing from two additional text rendering settings, light and strong. If the default was light before you upgraded to 10.8, you can restore it with defaults write -g AppleFontSmoothing -int 1.

High Resolution Guidelines for OS X: Advanced Optimization Techniques

In OS X v10.8, the default value of the NSFontDefaultScreenFontSubstitutionEnabled setting is NO. This setting determines whether or not text APIs (such as NSLayoutManager, NSCell, and the NSStringDrawing categories on NSString and NSAttributedString) substitute screen fonts when calculating layout and display of text.

Although screen font substitution will no longer be the default, using screen font might still be appropriate to support:

• Compatibility with documents created with previous versions of your app. The difference in glyph advancement measurements between integral and floating-point values can cause a change in text layout.
• Fixed-pitch plain text style output—for example, the Plain Text mode in Text Edit. To keep the OS X v10.7 screen font substitution behavior as the default, set the NSUserDefaults key NSFontDefaultScreenFontSubstitutionEnabled to YES.

To maintain the screen font setting on a per-document basis, specify NSUsesScreenFontsDocumentAttribute as a document attribute when you initialize an attributed string object.

defaults write -g NSFontDefaultScreenFontSubstitutionEnabled -bool true didn't seem to have (almost) any effect in most applications. But for some reason it disabled kerning in AppleScript Editor.

OS X normally will not display a character in the Private Use Area unless you manually set the font in the app. I understand this is intentional, since every font could have a different glyph at the same PUA code point, and it only makes sense to display something when the user specifies the font.

I think it should also work when the right font is selected via CSS or other markup in a document being read.

Some earlier versions of OS X did not have this "feature" and did display PUA stuff. I don't know how they chose which font to use when more than one had something at the code point selected.