Where Is The Library Caches Ats Folder Mac

admin 12.04.2020

Troubleshoot font issues in Adobe applications on Mac OS X

Where Is The Library Caches Ats Folder Mac 10
Where Is The Library Caches Ats Folder Mac Pro
Where Is The Library Caches Ats Folder Mac Version
Where Is The Library Caches Ats Folder Mac Os

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.

Apr 09, 2018 macOS Library Directory Details. The Library directories are where the system and your code store all of their related data and resources. In macOS, this directory can contain many different subdirectories, most of which are created automatically by the system. Jul 22, 2011 The Library folder that is now hidden in Lion is the Library folder in your User root folder (your Home folder, in other words). The difference is that each user has one of these (now hidden) Library folders, which affects his or her apps, extensions and settings etc.

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

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).

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)

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.

Where Is The Library Caches Ats Folder Mac 10

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:

Where Is The Library Caches Ats Folder Mac Pro

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.

Where Is The Library Caches Ats Folder Mac Version

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices Online Privacy Policy

The Library directories are where the system and your code store all of their related data and resources. In macOS, this directory can contain many different subdirectories, most of which are created automatically by the system. In iOS, the app installer creates only a few subdirectories in ~/Library (such as Caches and Preferences) and your app is responsible for creating all others.

Where Is The Library Caches Ats Folder Mac Os

Table A-1 lists some of the common subdirectories you might find in a Library directory in macOS along with the types of files that belong there. You should always use these directories for their intended purposes. For information about the directories your app should be using the most, see The Library Directory Stores App-Specific Files.

**Table A-1** Subdirectories of the Library directory
Subdirectory	Directory contents
`Application Support`	Contains all app-specific data and support files. These are the files that your app creates and manages on behalf of the user and can include files that contain user data. By convention, all of these items should be put in a subdirectory whose name matches the bundle identifier of the app. For example, if your app is named MyApp and has the bundle identifier `com.example.MyApp`, you would put your app’s user-specific data files and resources in the `~/Library/Application Support/com.example.MyApp/` directory. Your app is responsible for creating this directory as needed. Resources required by the app to run must be placed inside the app bundle itself.
`Assistants`	Contains programs that assist users in configuration or other tasks.
`Audio`	Contains audio plug-ins, loops, and device drivers.
`Autosave Information`	Contains app-specific autosave data.
`Caches`	Contains cached data that can be regenerated as needed. Apps should never rely on the existence of cache files. Cache files should be placed in a directory whose name matches the bundle identifier of the app. By convention, apps should store cache files in a subdirectory whose name matches the bundle identifier of the app. For example, if your app is named MyApp and has the bundle identifier `com.example.MyApp`, you would put user-specific cache files in the `~/Library/Caches/com.example.MyApp/` directory.
`ColorPickers` There is no Library folder in the Home directory I am looking at.What a colossal waste of time.New Question split by moderator from.The moderator supplied the question title. When tacked onto answered questions you can only hope a moderator stumbles across them and splits them off, which can take days, or may ever happen. My mac doesn't have a library folder. The original asker can modify the title by editing the question. Your moderator will not be offended if this is done.Note from moderator: new questions get answered much faster when asked as new questions.	Contains resources for picking colors according to a certain model, such as the HLS (Hue Angle, Saturation, Lightness) picker or RGB picker.
`ColorSync`	Contains ColorSync profiles and scripts.
`Components`	Contains system bundles and extensions.
`Containers`	Contains the home directories for any sandboxed apps. (Available in the user domain only.)
`Contextual Menu Items`	Contains plug-ins for extending system-level contextual menus.
`Cookies`	Contains data files with web browser cookies.
`Developer`	Contains data used by Xcode and other developer tools. Turn on your Mac or PC and connect it to the Internet. Library not found for so mac. Open the Music app or iTunes for Windows.
`Dictionaries`	Contains language dictionaries for the spell checker.
`Documentation`	Contains documentation files and Apple Help packages intended for the users and administrators of the computer. (Apple Help packages are located in the `Documentation/Help` directory.) In the local domain, this directory contains the help packages shipped by Apple (excluding developer documentation).
`Extensions`	Contains device drivers and other kernel extensions.
`Favorites`	Contains aliases to frequently accessed folders, files, or websites. (Available in the user domain only.)
`Fonts`	Contains font files for both display and printing.
`Frameworks`	Contains frameworks and shared libraries. The `Frameworks` directory in the system domain is for Apple-provided frameworks only. Developers should install their custom frameworks in either the local or user domain.
`Internet Plug-ins`	Contains plug-ins, libraries, and filters for web-browser content.
`Keyboards`	Contains keyboard definitions.
`LaunchAgents`	Specifies the agent apps to launch and run for the current user.
`LaunchDaemons`	Specifies the daemons to launch and run as root on the system.
`Logs`	Contains log files for the console and specific system services. Users can also view these logs using the Console app.
`Mail`	Contains the user’s mailboxes. (Available in the user domain only.)
`PreferencePanes`	Contains plug-ins for the System Preferences app. Developers should install their custom preference panes in the local domain.
`Preferences`	Contains the user’s preferences. You should never create files in this directory yourself. To get or set preference values, you should always use the `NSUserDefaults` class or an equivalent system-provided interface.
`Printers`	In the system and local domains, this directory contains print drivers, PPD plug-ins, and libraries needed to configure printers. In the user domain, this directory contains the user’s available printer configurations.
`QuickLook`	Contains QuickLook plug-ins. If your app defines a QuickLook plug-in for viewing custom document types, install it in this directory (user or local domains only).
`QuickTime`	Contains QuickTime components and extensions.
`Screen Savers`	Contains screen saver definitions. See Screen Saver Framework Reference for a description of the interfaces used to create screen saver plug-ins.
`Scripting Additions`	Contains scripts and scripting resources that extend the capabilities of AppleScript.
`Sounds`	Contains system alert sounds.
`StartupItems`	(Deprecated) Contains system and third-party scripts and programs to be run at boot time. (See Daemons and Services Programming Guide for more information about starting up processes at boot time.)
`Web Server`	Contains web server content. This directory contains the CGI scripts and webpages to be served. (Available in the local domain only.)