Troubleshoot fonts | Mac OS X

This document can assist you in resolving problems that occur when you install fonts or when using fonts with Adobe applications in Mac OS X. Font problems can manifest themselves in many different ways, including (but not limited to) the following:

• Fonts don't appear in the font menu of your applications.
• Fonts don't print correctly.
• Fonts in menus and dialog boxes have incorrect letters or characters.
• Fonts don't appear correct onscreen.
• Errors or crashes occur after installing fonts.
• Fonts are available to certain users only.

To benefit most from this document, perform the following tasks in order.

1. Check whether the font format is supported.

If you use an unsupported font format, the system can't display or print the font in applications.

Mac OS X supports the following font formats:

• .dfont
• Multiple Master (Mac OS X 10.2 and later only)
• OpenType (.otf)
• TrueType (.ttf)
• TrueType Collection (.ttc)
• Type 1 (PostScript)

2. Make sure the font is installed in the correct folder.

Mac OS X includes five font folders that allow you to use fonts in different ways. You can install fonts to as many folders as required because Mac OS X permits duplicate copies of a font in the system. If fonts have duplicate names, Mac OS X uses fonts—without regard to font format—from the following locations in the order listed:

1. Users/[user name]/Library/Fonts
2. Library/Fonts
   
3. Network/Library/Fonts
   
4. System/Library/Fonts (Avoid changing this folder. It contains .dfont fonts that Mac OS X requires for system use and display. For more information, see Mac OS X: Font locations and their purposes.)
5. System Folder/Fonts
   

Note: Fonts installed in System Folder/Fonts are available to all Classic, Carbon, and Cocoa applications.

To install a font in Mac OS X, do the following:

3. Check that both screen and printing files are installed. (PostScript fonts)

To use PostScript fonts in Mac OS X, install the bitmap (screen), or the suitcase containing the bitmap fonts, and outline (printer) fonts to the same folder. (Adobe bitmap font files use the font name. The outline files use a shortened, PostScript version of the font name [for example, "Isabe" for the Isabella font].) If an outline font file isn't installed, the font can print incorrectly. If the bitmap font file isn't installed, the font isn't available in the font menu.

4. Use Adobe Type Manager (ATM) with Classic applications.

ATM prevents fonts from appearing jagged onscreen and therefore helps PostScript fonts print more smoothly on nonPostScript printers when running applications in Classic mode. You can download a free version of ATM Light 4.6 from the Adobe website.

5. Troubleshoot third-party font management software.

Deactivate all font management utilities, such as Extensis Suitcase Fusion, Insider FontAgent Pro, or Linotype FontExplorer X. Attempt to perform the action that previously produced the problem (launching your application, accessing the font menu, and so on). Then do one of the following:

• If the problem recurs, move on to the next section below.
• If the problem doesn't recur, reactivate your font management utility. Use it to perform a binary isolation of the fonts by disabling 50% of your fonts and comparing the results with both halves. Then, continue this process for the half that reproduces the problem.

6. Remove font files.

Move font files from the Fonts folders in the Users, Library, and Network folders to the desktop or other location, and restart the computer. If the problem doesn't recur, one or more of the font files you moved is causing the problem. Replace font files a few at a time to determine which font is causing the problem. (For example, replace font files that start with A-E to the System/Library/Fonts folder, and then restart the computer. If the problem doesn't recur, add another small group of font files. If the problem does recur, one of the font files you just added could be the cause. Remove the font files, and add them back one at a time. Restart the computer each time until you find the particular font file that causes the problem.) When you find the font file that causes the problem, reinstall the font from the original media.

7. Use a current version of the font.

Make sure you are using the latest version of the font.

To check a font from the Adobe Type Library, select the font file, and choose File > Get Info > General to check the creation date. (If you're using PostScript fonts, check the creation date for each outline and suitcase file.) If the font's creation date is before 1992, a new version of the font could be available. For upgrade information, contact Adobe Customer Support at 1-800-833-6687.

8. Clean out the system font cache.

Corrupt font cache files cause fonts to appear damaged even if they are not. A common symptom is garbled text onscreen. Once the cache has been cleared, a corrupt font cache can be eliminated as the possible source of the problem. 

9. Troubleshoot for damaged fonts.

A system error can occur if an application accesses a damaged font. 

Note: If no adobefnt.lst file is found in the search, make sure the search criteria are set to 'any' in the Find dialog box.

To troubleshoot fonts if you use Font Book, do the following:

Important: Do not empty the Trash before the final step in this process.