Skip navigation
This discussion is archived

Leopard Font Organization

17978 Views 20 Replies Latest reply: Mar 3, 2008 12:57 PM by Guriboy RSS
1 2 Previous Next
Bill Fant1 Level 1 Level 1 (20 points)
Currently Being Moderated
Nov 9, 2007 11:33 AM
I did a standard upgrade when installing Leopard and I noticed some font issues shortly thereafter. I've sorted some of it out already, but my main question is how are fonts organized in Leopard? I'm finding fonts spread about and I'm still have a few duplicate font issues.

I believe 'Library >> Fonts' should be the default, but what about these:

- 'System >> Library >> Fonts'
- 'System >> Library >> Frameworks >> ApplicationServices.Framework ....(gets deeper)... Protected Fonts

I guessing some of these should have been consolidated and/or deleted upon upgrade.

Font Book is indicating some duplicates, but I'm having trouble finding them all. No fonts exist in the user directories and a search comes up empty handed. Also, I have not yet installed any third party fonts which I usually do by creating a unique library. Any suggestions?
MacBook Pro 17" / 2.4Ghz, Mac OS X (10.5)
  • SharonZ Calculating status...
    Currently Being Moderated
    Nov 9, 2007 8:07 PM (in response to Bill Fant1)
    The "auto activation" feature in Font Book prefs has nothing to do with whether the fonts are activated when they're first installed. This new Leopard feature is something that lets Leopard automatically (and temporarily) activate a font if you open a document that uses a font that isn't currently activated. The font doesn't even have to be installed in Font Book and be in a disabled state - Leopard will look thru your entire hard drive for font files and offer to open what you might need for that specific document.

    There's no way around the fact that FB automatically enables fonts when you install them. But you can make it easier to turn off all the new ones, depending how you organize your fonts. If you create a collection (not a library) and put all your fonts into that collection as you install them, you can then just turn off the entire collection. Since fonts can belong to more than one collection (a collection is just a sublist of installed fonts, gathered together for group manipulation like this), even if you also want to put them into collections like A and B and C, etc, you can start them in the NewInstalls collection so you can disable them all at once.

    Crashing is something else. It's highly unlikely that it's due to conflicts. It's possible that it's due to a bad or old (or bad and old) font here and there, but not conflicts. If you could narrow the issue down a little, we might be able to solve that.

    Mac OS X (10.4.5)
  • SharonZ Level 2 Level 2 (455 points)
    Currently Being Moderated
    Nov 9, 2007 8:16 PM (in response to Bill Fant1)
    /System/Library/Fonts does contain fonts that are absolutely necessary, but not all of them are; some can be removed.

    You can remove:
    -The Hiragino fonts
    -LeHei Pro
    -STHeiti fonts

    You can also remove some standards like Courier, Times, Zapf Dingbats, etc - but you shouldn't because they're used all over the place and you should have them; they're just not necessary to the system.
    So, you need:
    HelveLTMM, Helvetica LT MM
    Keyboard (won't show in Font Book)
    LastResort (won't show in Font Book)
    Lucida Grande
    Times LT MM

    Mac OS X (10.4.5)
  • SharonZ Level 2 Level 2 (455 points)
    Currently Being Moderated
    Nov 10, 2007 2:52 PM (in response to Bill Fant1)
    System >> Library >> Fonts (must have system fonts - cannot delete or move some)
    Library >> Fonts (fonts that come with OS X, but not required)
    Wonder for what reason.

    The /System/Library/Fonts are for the system's use (duh, you knew that).
    The /Library/Fonts folder is a place that applications, or "administrators" can put fonts that will be able to be shared by all users of a particular Mac, since the Mac is designed to be a shared machine, with multiple-account capability.

    That's why there's also a user's Fonts folder, so that each user of a Mac can have his/her own collection of Fonts that won't clog other users' Fonts menus.

    Font Doctor/Leopard not being happy...

    I'm always confused by what Font Doctor is supposed to be doing. A year or more ago, a friend's newspaper-publishing office finally moved up to OS X. We had to check and move thousands of fonts. I checked them all with Font Doctor; had to discard some. Then, while installing them thru Suitcase Fusion, which has Font Doctor with it, some of the already "fixed" stuff didn't pass; on the other hand, then some of the stuff that Font Doctor (standalone) said it couldn't fix, but Suitcase let it in after checking it, and they've been fine <sigh>.
    Mac OS X (10.4.5)
  • James_L. Ryan Level 1 Level 1 (20 points)
    Currently Being Moderated
    Nov 10, 2007 6:38 PM (in response to Bill Fant1)
    I've created several libraries of fonts, each library containing the fonts acquired from a given source. Currently the libraries are Adobe, Apple, iLife, iWork, and Microsoft, each library containing all of the fonts obtained from the designated source. All of the fonts for a given library are kept in a separate folder. Thus, ignoring the fonts in System/Library/Fonts, there are five font folders.

    In addition, the fonts in each of these libraries have been exported via Font Book so that all of the files for a given font family are contained in an appropriately named folder inside of the library folder.

    Other than the fonts in System/Library/Fonts, the five aforementioned libraries of fonts are kept in Users/Shared/Fonts. An advantage of having the fonts there instead of Library/Fonts is that, given that Library/Fonts is the default place where applications tend to install there fonts, it is easy to determine which fonts an application has installed.

    So far, Font Book has dealt well with this organizational structure. I did make a single pass through the five libraries and resolved duplicates.

    The final conclusion is that this organizational structure provides a good method of managing fonts via Font Book.
    MacBook Pro 17", Mac OS X (10.5)
  • MarkDouma® Level 6 Level 6 (9,845 points)
    Currently Being Moderated
    Nov 11, 2007 1:24 AM (in response to Bill Fant1)
    Bill Fant1 wrote:
    - 'System >> Library >> Frameworks >> ApplicationServices.Framework ....(gets deeper)... Protected Fonts

    Do not under any circumstances delete the fonts in the /System/Library/Frameworks/ApplicationServices.framework/...
    /Frameworks/ATS.framework/Versions/A/Resources/ProtectedFonts/ folder!

    The ATS.framework is the Apple Type Services framework, which contains the ATSServer (the background process that handles everything to do with fonts: activating, deactivating, caching, etc.). As you can see in the path above, those are meant to be protected fonts; Leopard has a "self-healing" feature that's meant to restore the core fonts back into the /System/Library/Fonts/ folder if necessary. (Prior to Leopard, if you deleted LucidaGrande.dfont from the /System/Library/Fonts/ folder, upon restart your Mac would hang indefinitely on login with a blue screen. There was no easy way to fix this (unless you consider starting up in single-user mode and moving files around using the command line to be easy).

    Hope this helps....
    Dual 2.7GHz PowerPC G5 w/ 2.5 GB RAM; 17" MacBook Pro w/ 2 GB RAM -, Mac OS X (10.5)
  • Kevin Neal Level 2 Level 2 (475 points)
    Currently Being Moderated
    Nov 15, 2007 1:23 PM (in response to MarkDouma®)
    Pro graphics/ repro users might have to remove protected fonts such as helvetica neue because it clashes with the full (expensive) set of postscript versions we have.

    dfonts aren't suitable for professional printing and need to be removed so they don't clash
    Powerbook 15.2, Mac OS X (10.4)
  • SharonZ Level 2 Level 2 (455 points)
    Currently Being Moderated
    Nov 15, 2007 5:14 PM (in response to Kevin Neal)
    Kevin Neal wrote:
    Pro graphics/ repro users might have to remove protected fonts such as helvetica neue because it clashes with the full (expensive) set of postscript versions we have.

    dfonts aren't suitable for professional printing and need to be removed so they don't clash

    Both Helvetica and Helvetica Neue are absolute musts for OS X; if they're removed, you'll have all sorts of problems. As long as you have other versions of them available and activated, you'll be fine, but a blanket recommendation to remove these fonts can be problematic if users don't realize how important they are. It's a particular problem for pros because they turn fonts on and off so often, and may remove the system's Helvetica, say, and then turn their version off in Suitcase or whatever management program they're using. Unless a user is very sure of what fonts are where, and will ALWAYS leave certain fonts, like Helvetica and Helvetica Neue on, it's safer to leave the system versions in, add your versions, and turn the right ones on when you need them to avoid "clashes" - which, thank goodness, aren't like font clashes of old - the worst that usually happens is that you wind up using the wrong version of the font, not crashing your whole system.

    The same goes for many of the dfonts - not that you'll be doing much designing with Geneva or Monaco!
    Mac OS X (10.5)
  • Magnus Lewan Level 4 Level 4 (3,655 points)
    Currently Being Moderated
    Nov 16, 2007 7:51 AM (in response to Bill Fant1)
    Bill Fant1 wrote:
    Can someone post the list of fonts (font file names) that should be installed for Leopard (with clean install)

    Someone may have compiled a list, but Apple has not done that yet. For what it is worth, here is the list of fonts in 10.4:
    PowerBook G4, Mac OS X (10.5)
  • Kevin Neal Level 2 Level 2 (475 points)
    Currently Being Moderated
    Nov 16, 2007 12:19 PM (in response to SharonZ)
    problem with that is the dfont version of helvetica neue will be active and so is going to get used in Quark or Indesign, which is bad news because dfont should be avoided,

    Also if you put a full bought set of helvetica neue in your system font folder instead of the dfont, OS X won't recognise it for internal use
    Macbook Pro 2.16 Ghz 2Gb RAM, Mac OS X (10.5)
  • James_L. Ryan Level 1 Level 1 (20 points)
    Currently Being Moderated
    Nov 17, 2007 12:26 PM (in response to Bill Fant1)
    Here are the contents of /Library/Fonts immediately following a clean installation of Leopard. The list is by family. If there are more than a single font face in a family the number is shown in parentheses following the family name.

    Al Bayan (2)
    American Typewriter
    Andale Mono

    Apple Chancery
    Apple LiGothic
    Apple LiSung
    Apple Myungjo
    Arial (4)
    Arial Black
    Arial Hebrew (2)

    Arial Narrow (4)
    Arial Rounded MT Bold
    Arial Unicode MS

    Big Caslon
    Brush Script MT
    Chalkboard (2)
    Charcoal CY
    Comic Sans MS (2)

    Corsiva Hebrew (2)
    Courier New (4)
    DecoType Naskh
    Devanagari MT (2)
    Euphemia UCAS (3)

    GB18030 Bitmap
    Geneva CY
    Georgia (4)
    Gill Sans
    Gujarati MT (2)
    Curmukhi MT

    Helvetica CY
    Hiragino Kaku Gothic Pro (2)
    Hiragina Kaku Gothic Std
    Hiragina Kaku Gothic StdN
    Hiragino Maru Gothic Pro
    Hiragino Maru Gothic ProN

    Hiragino Mincho Pro (2)
    Hoefler Text

    LiSong Pro
    Marker Felt
    Microsoft Sans Serif
    Mshtaken (4)

    New Peninim MT (4)
    Osaka (2)
    Plantaget Cherokee
    Raanana (2)

    Tahoma (2)
    Times New Roman (2)

    Trebuchet MS (4)
    Verdana (4)
    Winddings 2
    Wingdings 3
    MacBook Pro 17", Mac OS X (10.4.8)
1 2 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.