Mar 25, 2020 Fortunately, learning how to install fonts in Windows 10 is easier than you might think. Once your font library loads, simply drag your new font from the destination location in File Explorer.
- Sep 22, 2017 There is no advantage whatsoever to putting third party fonts into the System folder. As Niel noted, put them in the root /Library/Fonts/ folder if you want all users on that Mac to have access to it. If you want to limit use of the font to yourself, put it in the Fonts folder of your user account.
- How to Install Fonts With Font Book. Download a new font on the internet. Find the file in your Downloads folder (or wherever you send items you download) and double-click it. If the item downloads as a zip file, double. Font Book will open automatically if the file.
- Dec 22, 2017 Smooth Fonts On Windows 10. Install MacType. The app supports English but you will find most of the options in the installer still appear in Chinese. Go for a custom install and install only the basics. Once the app has been installed, you have to.
- Sep 09, 2008 If you have the Adobe CS2 or CS3 programs installed, you can place such fonts in the /Library/Application Support/Adobe/Fonts/ folder to use them in the Adobe apps. Those are the only applications that Windows Type 1 PostScript fonts will with.
- But avoid to install too many fonts at one time because that slows down the system. A lot of programs have to load to memory all installed fonts to be able to run. So it is better to put fonts you use regularly in the Fonts.
Fonts are not just files, but rather system plug-ins, similar in ways to an extension or add-on application. When added and activated, they load into memory and are associated to programs by the system so programs can make use of them and show information about them.
As a result, should a font be damaged, or perhaps conflict with another font, then not only might it lead to improper characters being used, or alignments being off in documents, but also crashes and hangs for programs that access these fonts.
Font Conflicts
Font conflicts occur when two fonts of different type faces (or perhaps even more subtle difference) have the same internal name. For instance, the system’s internal font Monaco has a specific look and character layout for use with the system, and many programs rely on this font in this manner. However, if a font from a third-party with the name “Monaco,” or perhaps a modified version of Monaco is installed, then the system will identify two of the same type and not know which to use. In these cases, the system or application will use the first one it identifies, which may be the improper one and cause visual conflicts.
Font conflicts and damaged fonts can cause a document to display garbled text (click image for larger view).
In most cases, font conflicts occur because someone installed a duplicate of the exact same font, so one resides in a system library such as the system’s font folder (Macintosh HD > System > Library > Fonts), or the global font folder (Macintosh HD > Library > Fonts). These two library folders contain settings and resources that apply to the entire system and all users. The system folder contains core fonts that Apple provides and which are required in unaltered states for OS X to run. These take precedence over other fonts; however, a program can install a font in the global font folder that is the same as one in the system’s font folder, and result in a font conflict.
Similarly, a user can install a font library for their uses, which may contain duplicates of fonts already in the system or global fonts folder, and again result in a font conflict.
Damaged fonts
In the case of damaged fonts, the system may attempt to load them and either not be able to and result in a hang or crash, or will load them and you will see corrupt symbols appear instead of the desired font face. At other times, the symptoms may not be so apparent, such as a fault with only specific characters that cause problems when they are displayed.
For older and incompatible fonts, the system will usually just not load them; however, there may be instances where it tries and results in a persistent error, slow loading, or some other odd behavior either with the system or with the specific program you are using, that can frustrate your workflow.
Troubleshooting
Expanding the font with the error shows the only problem here is a duplicated font file. This is a relatively minor issue, especially if the font is an unmodified duplicate (click image for larger view).
There are various ways to troubleshoot and repair font problems in OS X. This procedure essentially involves identifying any problematic fonts, and then removing, disabling, or replacing them.
Note that for any font-related procedure, you keep track of what you do and where you move or otherwise place fonts, to be able to undo any changes you make. Also keep in mind that any changes you make outside of your home folder will potentially affect other users on your system.
1. Font Book
If you use a third-party font manager for your fonts, then be sure it is updated and then open it to manage your font collection. Depending on the program you use, there may be routines you can run to check your various fonts for conflicts and other errors. In Apple’s Font Book, you can click the All Fonts collection, followed by clicking a font and then pressing Command-A to select all fonts on the system. Then choose “Validate Fonts” from the File menu, and the program will check for conflicts, compatibility, and damage to your fonts.
While you can usually get away with minor errors found in the font validation routine (noted by a yellow circle with an exclamation point in it), you might want to investigate the cause for this problem.
If you see any errors that are colored red, then this indicates a problem that will likely cause a disruption to programs and services that use this font, and you should consider disabling, removing, or reinstalling the font.
Right-clicking a font in Font Book gives you options to manage it (click image for larger view).
In all cases, from the validation window you can click the checkbox next to a font to select it, and then click “Remove Checked” to delete the selected fonts. Alternatively, you can identify the fonts and close the validation window, followed by managing them in the Font book window in the following ways:
Resolve Duplicates
Select all fonts and right-click them, followed by choosing “Resolve Duplicates.” This will disable any global fonts that are in conflict with those in your home folder, and keep the ones in your home folder active. This setting is for your account only, so global fonts will still be active for other users.
Disable FontsSelect all fonts and right-click them, followed by choosing “Resolve Duplicates.” This will disable any global fonts that are in conflict with those in your home folder, and keep the ones in your home folder active. This setting is for your account only, so global fonts will still be active for other users.
You can select a font set by holding the Command key and clicking individual fonts, or by creating a new collection (in the File menu) and dragging fonts to this collection. With your set created, you can right-click it and choose the option to disable the set. This will turn off these fonts for your account, but keep them installed for other accounts to use. Note that this can be done for an individually selected font, but it may be easier to manage a number of fonts through a collection.
Remove Fonts
The final option is to select a font, selection of fonts, or a collection, and then again right-click it but this time choose the option to remove the fonts. This will delete them and make them unavailable to any user account in the system.
The final option is to select a font, selection of fonts, or a collection, and then again right-click it but this time choose the option to remove the fonts. This will delete them and make them unavailable to any user account in the system.
2. Manual management
While the font book application and similar font managers might be preferentially used for dealing with font problems, you can also approach this manually. As mentioned above, fonts in OS X are in the following three folders, though the last two are the only ones you should modify:
Macintosh HD > System > Library > Fonts
Macintosh HD > Library > Fonts
Macintosh HD > Users > username > Library > Fonts
Macintosh HD > Library > Fonts
Macintosh HD > Users > username > Library > Fonts
If you go to the last two of these folders, you can move fonts out of the folders to disable them. Unfortunately doing things this way can be a bit of a burden, but is the only way to approach this manually.
Sorting the Fonts folder by date added can help isolate those you installed with a particular program, or otherwise. This can also help you remove all of these at once (click image for larger view).
It may help to put the Font folder in list view, and then sort the list by “Date Added,” which will categorize the items in it by when they were placed in this folder. This can help group fonts by when they were installed, as opposed to when they were created or modified, which can sometimes be years differences for fonts in the same collection.
3. Clearing caches
Another possible problem can be if your Mac’s font cache is corrupted. When fonts are installed, they are loaded into a cache for quick access, and while a font on disk might be fine, if the cache is not working properly then you may experience problems similar to the font files themselves being corrupted.
There are two ways to clear font caches in OS X. The first is to simply reboot into Safe Mode by holding the Shift key immediately when you hear the boot chimes at startup. When this mode loads, a progress bar should appear, during which the system will run various checks and maintenance routines, one of which is to clear the font cache.
The second approach is to use the Terminal, which can be done by running the following command from within an administrative account:
Note that this command will require you to enter your password, which will not be shown when typed.
Handling third-party font managers
Third-party font managers are sometimes the only way to properly manage fonts for some projects and uses. However, be sure you only use one font manager to manage your fonts. If you use a third-party font managers like Suitcase Fusion, FontExplorer X, or FontAgent Pro, then be sure to uninstall any others. While you can still keep Apple’s Font Book on your system, avoid using it to run any font management functions.
In addition, be sure to keep any font managers updated to the latest versions. While rare, there have been times that font managers have not been updated to match a version of OS X, resulting in problems with font management in the new OS version. This is especially true for major upgrades to OS X (such as going from OS X 10.8 to OS X 10.9), as opposed to step updates (ie, 10.8.2 to 10.8.3).
As with any software you use, be sure to check with your font manager’s developer for compatibility before updating any system software, and be sure to keep the latest version of the software installed on your system.
Troubleshoot font issues in Adobe applications on 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.
![Mac system font size Mac system font size](/uploads/1/2/6/2/126263970/246134713.png)
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:
- Users/[user name]/Library/Fonts
- Library/Fonts
- Network/Library/Fonts
- 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.)
- 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:
- Quit all applications (to use the font in those applications).
- Log in:
- If you're installing fonts to the Users/[user name]/Library/Font folder, log in with your user name.
- If you're installing fonts to the Library/Fonts folder, log in as Administrator.
- If you're installing fonts to the Network/Library/Fonts folder on a networked server, contact your network administrator.
- Drag the font files from the original media (for example, a CD) to one or more of the following folders on the hard disk:Note: When installing PostScript fonts, drag both the outline font file and bitmap font suitcase to the appropriate folder. (In Mac OS X, font suitcases look and behave like other font files. You can't open them by double-clicking the file as you can in Mac OS 9.)
- System Folder/Fonts, to access the font in applications running in Mac OS X and applications running in Classic mode (Mac OS 9)
- Library/Fonts, to access the font in all applications by all users in Mac OS X. (The font isn't available in applications running in Classic mode.)
- Users/[user name]/Library/Fonts—used by a specific user in Mac OS X. (The font is available in all applications in Mac OS X only when you log in as the specified user.)
- Network/Library/Fonts—accessed by remote users on a networked file server running Mac OS X over a local area network (LAN)
![System System](/uploads/1/2/6/2/126263970/313740363.jpg)
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.
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.
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.
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.
A system error can occur if an application accesses a damaged font.
- Drag the contents of the Library/ Fonts folder to a new folder on the desktop. (If you manually added fonts to the Library/ Application Support/ Adobe/ Fonts folder, also drag those fonts to the new folder.)
- Type AdobeFnt.lst, select the system drive, and then press Return.
- Delete all AdobeFnt.lst files found (for example, AdobeFnt10.lst).
- Restart InDesign. InDesign creates new AdobeFnt.lst files.
- Try to re-create the problem. Then, do one of the following:
- If the problem doesn't recur, move one font back to the Library/Fonts folder, and then repeat steps 5-6 until you identify the problematic font.
- If you have a font management utility, restart it and activate fonts in small groups or individually to identify the problematic font.
- If the problem recurs, move the contents of the new folder on the desktop back to the Library/Fonts folder.
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.
- Navigate to Home/Library/Preferences and remove the following files:
- com.apple.fontbook.plist
- com.apple.ATS.plist
Note: The first file is the preferences file for Font Book. The second file specifies the fonts you disabled in Font Book. After you delete com.apple.ATS.plist, all previously disabled fonts load when you next log in. If you installed hundreds or thousands of fonts, the performance of your system could be slow when all previously disabled fonts are loaded. - Delete your font cache. To delete your font cache, do the following:
- Locate and delete your font cache folder. For example, if you are the first user defined on your Mac, the folder is named 501. If you are the second user, the folder is named 502.
Note: If you use Fast User Switching, several 501.xxx, 502.xxx folders could be in the ATS folder. Move them to the Trash.
- If requested to authenticate trashing any of these folders, provide your Administrator password.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
Access System Library Mac
Legal Notices | Online Privacy Policy