Font Book question
I use Font Book to disable the Classic Mac OS fonts, but it often (but not always) enables them again after a restart, which is very annoying. Is there a fix for this, or an alternative simple way to disable them?
thanks
Move them out of your Fonts folder.
Similar Messages
-
Not sure if this is the best place for them but I can't find anywhere else.
Do I need to keep font book open to have the fonts working? Whenever I close the window, the little black triangle disappears, which would indicate that the app has quit. Does that mean I have to have it minimised the whole time if I don't want the window up on screen?
When I added all my fonts to Font Book, it copied them all to the default directory, which is fine. During the process, a window opened showing corrupt fonts. Since I did not ask it to install these fonts, can I assume that those corrupt fonts are still sitting in my original font directory rather than sitting inactive in Font Book's default location?
In the list of corrupt fonts, I tipped open the triangle next to one or two. There was quite a detailed diagnostic & it said it was the "Font Table Directory" that was corrupt. Is this repairable?
I've now closed that window with details of corrupt fonts. Can I re-open it?
That'll do for now. Thanks."Do I need to keep font book open to have the fonts working?"
No.
As for the corrupt fonts, try out the following:
*Validating your fonts:*
Font Book>File>Validate Font
Check for duplicate fonts.
Applications>Font Book
Select “All Fonts”
If you see any “black dots” next to any fonts this mean you have duplicates and/or multiple versions of these fonts.
To clean this up, select a “black dotted” font or the Apple + click to select multiple dotted fonts;
Edit>Resolve>Duplicates.
What the above does is turns off the duplicates & multiple version fonts. Not delete them.
More than likely the “extras” were installed by other programs and/or other users.
Clear out font caches
Use FontNuke. It does all the work for you. And, best of all it’s FREE. -
How do I use the Japanese fonts in Font Book in a Pages document?
How does one use the Japanese fonts in Font Book in a Pages document. Pages has its own fonts but I cannot get the Japanese fonts into it.
To type japanese on a computer you change the keyboard, not the font. Go to system prefs/keyboard/input sources and add Japanese/Kotoeri to the list, then select Hiragana in the "flag" menu at the top right of the screen, then type. The font will take care of itself.
http://redcocoon.org/cab/mysoft.html
If you have any further questions, just ask. -
How do I use a font variation in a pages document? or other app for that matter? I no longer have the "viewer" - glyph option in the special characters pane (under edit in toolbar). I know the varaition ia available because I can see it in my font book. I depended on that alot so I need to find a way to still use character and embellishments. I don't want to have to go back to my od computer (from2007) Please Help!
I really don't understand.
The menu item is available :
Maybe, you didn't activate the tool :
Yvan KOENIG (VALLAURIS, France) mardi 2 août 2011 23:10:17
iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0
My iDisk is : <http://public.me.com/koenigyvan>
Please : Search for questions similar to your own before submitting them to the community
To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer ! -
I need a font book factory reset & a clean slate
My font book is is a mess! I have duplicate fonts in about 4 different directories (my fault) and want a fresh start. I did an "export" of my fonts but I am unsure how to do a factory reset. I've read the Font Management in OS X doc but am unclear if clearing the cache will bring me back to just the basic system fonts or only clears the history.
Do I need to go in and delete ("file ----> remove font") the fonts in font book one by one and THEN clear the cache before reinstalling the ones I want in the ONE directory folder where I want them to live? (lesson learned). I have 1200 (not including the duplicates) fonts that I need to sift through and am looking for the fastest way to do this without losing the key system fonts for Mac, Office 2011 and Adobe CS5 Creative Suite.
Is that amount of installed fonts still manageable with font book or should I be looking at a different font management solultion? I can't answer that for myself until I make it manageable with only ONE copy of each font
Thanks in advance for your help! I promise that I've read through this site and have been googling all day but haven't been sure about resetting the it all back to square one
TaraThere isn't an easy, singular answer to your question, though it would be fairly straightforward if it weren't for Office. I am curious how you arrived at 4 directories of fonts. There are only three Fonts folders OS X looks at. The ones in the System folder, the main Library folder, and the one in the active user account. Since you shouldn't even be looking in the System folder (if you don't know what you're doing), the only two places you should have any fonts you've added would be the main Library and your account.
Anyway, start by launching Font Book. Delete any Font sets or Library sets you have created. Close Font Book. Create a new folder on the desktop. Call it "mine". Anything you want really, just so it refers to the fonts in your user account. Go to the Fonts folder in your user account and move all fonts out of that folder to the new one on the desktop. Create another new folder on the desktop named "lib". Open the /Library/Fonts/ folder and move all fonts into the second new folder. Both the /Library/Fonts/ folder, and the Fonts folder in your user account should be empty.
Follow the instructions at the bottom of Font Management in OS X to restore all fonts from the Snow Leopard DVD. You will be using Pacifist to restore both the System and Library fonts. When you're done, your fonts will be back to the way the were when you first installed OS X.
From the desktop folder you named "lib". Move Hoefler Text.ttc and STHeiti Medium.ttc to the /Library/Fonts/ folder. Replace the versions you just restored with these newer versions. They were updated in 10.6.5.
Office 2011 installs many newer versions of fonts OS X comes with. Move these fonts from the 'lib" folder into the /Library/Fonts/ folder so you again replace the ones you just restored.
Arial.ttf
Arial Italic.ttf
Arial Bold.ttf
Arial Bold Italic.ttf
Brush Script.ttf
Times New Roman.ttf
Times New Roman Italic.ttf
Times New Roman Bold.ttf
Times New Roman Bold Italic.ttf
Verdana.ttf
Verdana Italic.ttf
Verdana Bold.ttf
Verdana Bold Italic.ttf
Wingdings.ttf
Wingdings 2.ttf
Wingdings 3.ttf
Here's where it gets a bit trickier. Office 2011 also installs a number of old fonts which conflict with the newer .ttf OpenType fonts. Delete these from the "lib" folder on your desktop. Note that they do not have a file extension.
Andale Mono
Arial Black
Arial Narrow
Arial Rounded Bold
Comic Sans MS
Georgia
Impact
Tahoma
Trebuchet MS
Without being able to see what you have left in the "lib" folder, I can't easily say what you can move back into the /Library/Fonts/ folder. So I'll list everything else Office 2011 installs that you can move back in. Office uses many of these for its supplied templates. Cambria is the default font family for Word.
Abadi MT Condensed Extra Bold
Abadi MT Condensed Light
Baskerville Old Face
Batang.ttf
Bauhaus 93
Bell MT
Bernard MT Condensed
Book Antiqua
Bookman Old Style
Bookshelf Symbol 7.ttf
Braggadocio
Britannic Bold
Calibri Bold Italic.ttf
Calibri Bold.ttf
Calibri Italic.ttf
Calibri.ttf
Calisto MT
Cambria Bold Italic.ttf
Cambria Bold.ttf
Cambria Italic.ttf
Cambria Math.ttf
Cambria.ttf
Candara Bold Italic.ttf
Candara Bold.ttf
Candara Italic.ttf
Candara.ttf
Century
Century Gothic
Century Schoolbook
Colonna
Consolas Bold Italic.ttf
Consolas Bold.ttf
Consolas Italic.ttf
Consolas.ttf
Constantia Bold Italic.ttf
Constantia Bold.ttf
Constantia Italic.ttf
Constantia.ttf
Cooper Black
Copperplate Gothic Bold
Copperplate Gothic Light
Corbel Bold Italic.ttf
Corbel Bold.ttf
Corbel Italic.ttf
Corbel.ttf
Curlz MT
Desdemona
Edwardian Script ITC
Engravers MT
Eurostile
Footlight Light
Franklin Gothic Book Italic.ttf
Franklin Gothic Book.ttf
Franklin Gothic Medium Italic.ttf
Franklin Gothic Medium.ttf
Gabriola.ttf
Garamond
Gill Sans MT Bold Italic.ttf
Gill Sans MT Bold.ttf
Gill Sans MT Italic.ttf
Gill Sans MT.ttf
Gill Sans Ultra Bold
Gloucester MT Extra Condensed
Goudy Old Style
Gulim.ttf
Haettenschweiler
Harrington
Imprint MT Shadow
Kino
Lucida Blackletter
Lucida Bright
Lucida Calligraphy
Lucida Console.ttf
Lucida Fax
Lucida Handwriting
Lucida Sans
Lucida Sans Typewriter
Lucida Sans Unicode.ttf
Marlett.ttf
Matura Script Capitals
Meiryo Bold Italic.ttf
Meiryo Bold.ttf
Meiryo Italic.ttf
Meiryo.ttf
Mistral
Modern No. 20
Monotype Corsiva
Monotype Sorts
MS Gothic.ttf
MS Mincho.ttf
MS PGothic.ttf
MS PMincho.ttf
MS Reference Sans Serif.ttf
MS Reference Specialty.ttf
MT Extra
News Gothic MT
Onyx
Palatino Linotype Bold Italic.ttf
Palatino Linotype Bold.ttf
Palatino Linotype Italic.ttf
Palatino Linotype.ttf
Perpetua Bold Italic.ttf
Perpetua Bold.ttf
Perpetua Italic.ttf
Perpetua Titling MT
Perpetua.ttf
Playbill
PMingLiU.ttf
Rockwell
Rockwell Extra Bold
SimSun.ttf
Stencil
Tw Cen MT Bold Italic.ttf
Tw Cen MT Bold.ttf
Tw Cen MT Italic.ttf
Tw Cen MT.ttf
Wide Latin
Anything you have left in the "lib" folder on your desktop will either be duplicates, or fonts installed by other third party apps. That will essentially be true of any fonts you moved out of your user account. I can't tell you which, if any of these, would need to be moved back in. For now, combine the two into a single folder and store them away anywhere not in any of the three Fonts on the hard drive. There will be a bunch of them as CS5 installs a slew of fonts. None of which it needs to operate.
That's as far as I can help with the fonts themselves.
Now open Disk Utility and run a Repair Permissions on your startup drive. Moving the fonts around will cause them to have permissions OS X doesn't like. Mainly just because you moved them back into the /Library/Fonts/ folder and it will want to change the permissions to OS X as the owner simply because of where they are.
Last few things to do.
Restart your Mac and immediately hold down the Shift key when you hear the startup chime to boot into Safe Mode. Keep holding the Shift key until you see a progress bar towards the bottom of the screen. You can let go of the Shift key at that point.
OS X asks you to log in (you will get this screen on a Safe Mode boot even if your Mac is set to automatically log in). Let the Mac finish booting to the desktop and then restart normally. This will clear Font Book's database and the cache files of the user account you logged into in Safe Mode.
Next to take care of the System's font cache files.
Close all running applications. From an administrator account, open the Terminal app and enter the following command. You can also copy/paste it from here into the Terminal window:
sudo atsutil databases -remove
Terminal will then ask for your admin password. As you type, it will not show anything, so be sure to enter it correctly.
This removes all font cache files. Both for the system and the current user font cache files. After running the command, close Terminal and immediately restart your Mac.
Last step when back at the desktop. Launch Font Book so it can create a new database based on the fonts currently in the drive's three Fonts folders.
There should be no duplicates. Everything OS X and Office installs will be available. -
Font Book - after 10.5.2 update, font has no preview and doesn't work
Help me, this problem is driving me crazy!
I've done a clean install of Leopard 10.5.0 on my MacBook Pro, on an external firewire drive (I want to keep my Tiger install as is at the momement). I install the adobe postscript Type 1 font Carta, which is a map symbol font, in Font Book. Font Book shows the preview of the font, which looks fine. I download a fresh 10.5.2 update and install it, restart. Now in Font Book, no preview of the Carta font, the preview window is blank, or it shows whichever font was displayed before, ie if I click on Arial then on Carta, the preview of Arial remains. Double clicking on the font itself opens Font Book main window, but no preview. The Opentype version of this font does exactly the same thing. Font Book validates the fonts as being okay.
When it comes to applications, Word 2004 will display the font, but character spacing is all over the place. Indesign CS3 will display the first 96 characters correctly, but after that it puts in a 'missing font' highlighted space. Opening the font with Linotype FontXplorer, the preview shows the font, though it seems to be missing the 'Z' and 'z'. Character Palette shows all glyphs in the font correctly, but double clicking on any above the first 96 puts in a 'missing font' space in Indesign. The trouble is the characters I need to use are all above this point in the font! Basically, it seems that the OS update has changed the font mapping.
The Font Book preview problem doesn't just happen to Carta, it seems to happen on a number of other fonts, mostly symbol fonts, some that I've created using Fontographer. All work perfectly in OS9 and 10.4.11. Even more annoyingly, other colleagues with different Macs on 10.5.2 are having no problems. I have done all the usual voodoo of deleting font caches, rebuilding permissions, even gone back to the font CDs to get the originals, reinstalled, etc.
I have installed Leopard from 2 different DVDs, on two different intel machines (a MacBook Pro and a Mac Pro), and swapped the Firewire drive onto a G4 (I installed it so it would boot both the G4 and the MBP), and always the same result. I'm going to install an HD internally on the G4, install Leopard and see if the same thing happens.
Anybody got any useful suggestions?I'm slowly getting to a solution, or at least a reason, for this problem. It seems that Leopard has tighter requirements on fonts for the languages they support. The Carta info in Tiger looks like this:
!http://www.biscuit.demon.co.uk/carta/cartainfotiger.gif!
Whereas under Leopard it says:
!http://www.biscuit.demon.co.uk/carta/cartainfoleo.gif!
Indonesian as the language under Leopard?! All the other fonts that I have problems with generally have NO language when I look at the info panel under Leopard AND Tiger. But Tiger seems to cope with them with my language set to British English. At least this may explain why the character encoding goes a bit crazy under Leopard.
Out of a peculiar sort of masochistic interest, I went through all of the default languages, plus a few others, that Leopard installs, seeing the effect of changing the language on the Font Book preview. I should just say that the Font Book Repertoire is always the same for all the languages, and the same info is displayed each time too. I'm now convinced it's the character mapping that changes when different languages are selected as the default.
Font Book Repertoire:
!http://www.biscuit.demon.co.uk/carta/cartaenglishrep.gif!
All the following languages displayed the preview correctly: English, Francais, Deutsch, Espanol, Italiano, Portugues, Svenska, Norsk Bokmal, Dansk, Suomi.
The preview looked like this:
!http://www.biscuit.demon.co.uk/carta/carta_english.gif!
The following languages showed the same behaviour as British English, in that NO preview showed, it would display the font preview of the previously selected font: Portugues (Portugal), Austalian English, Canadian English, US English, Espanol (Espana)
Changing to languages with different alphabets tended to show different things. Not sure if I've correctly identified the languages.
The two Chinese (I think) languages - AaBbCc characters only
Japanese (I think) - a to m, A to M, numbers 1 to 0
Korean (I think) - two arrows usually mapped to singe and double quotation marks, and ABcdEFgh 1234567890 - see this image:
!http://www.biscuit.demon.co.uk/carta/carta_korean.gif!
Russian (I think) - 1234567890 ("*#%&@`)
Polski - This produced the most, dropping several characters from the main alphabet, but adding a load that usually map to ("*%&') - see below:
!http://www.biscuit.demon.co.uk/carta/carta_polski.gif!
This all means that I have to stick with "English" as my Language, rather than "British English". I have yet to reinstall CS3, but I'll do this without changing the language, and hopefully CS3 with get the encoding correct.
Questions? Comments? Sorry about all the images. -
Font Book: Managing Fonts, Duplicates, Warnings etc... Need Help!
How this all started...
I have a lot of fonts. I use them for design purposes, and recently added a bunch of new ones.
As a result, I had a problem with an Adobe program and the font displayed in the workspace.
I figured out which one caused it and deleted it. (I've never used it before, and it wasn't a common font, so I didn't really care).
Problem with that solved.
So I figured that I ought to go through Font Book and check everything else and started Validation (under User).
I had several Errors, Duplicates and Warnings.
I (maybe naively) allowed Font Book to "Resolve Duplicates".
QUESTION 1 (a) (b): Could letting Font Book resolve duplicates create any problems? and how does it decide what to trash?
I also let Font Book move all the Error fonts to my empty Trash Folder.
- I then moved all those to an empty folder on my desktop.
I then moved all the Warning Fonts to another empty folder on my desktop.
So now, in User fonts, there are currently no problem messages.
This is where it gets a little trickier...
In "All Fonts" or "Computer" there are no caution symbols adjacent to any fonts, but if I run Validation, I get a lot of duplicate fonts.
For example... Arial exists in:
Library/fonts
User/Library/fonts
Library/Fonts/Microsoft
QUESTION 2: Do I need to address these? and if so, will that have an effect on any programs that use those fonts?
* I did some research on this, and found an article at Mac World, discussing this, but I don't feel any better/wiser after reading it or the comments...
"Problem" since resolving duplicates and/or moving warning and error fonts (from User):
Since I resolved duplicates, and moved the error and warning fonts, I've noticed some "minor" changes in appearance with websites.
Such as in Hotmail, and a website that I'm a member; the font displayed is now just slightly different.
Albeit, the difference is very subtle, (but as a designer, I noticed this right away) and my concern is how this may affect any design work I do, if somehow the change I'm seeing is more of an error.
* I have to make an assumption that its a font used in scripts (like Arial, Helvetica, etc, etc) that use my fonts for display.
QUESTION 3: So the big question is, how the heck do I address that now???
About the Warning Fonts:
For the most part, the fonts that came up as "minor warnings", showed the message 'kern' table structure and contents.
- I know that "kern" is suppose to be the spacing between characters.
QUESTION 4: So, why does Font Book care and warn about the "table structure and contents" of font spacing between characters, for any font???
QUESTION 4b: If that's NOT what that means, then I'd appreciate a plain English definition (perferably a source from Apple directly).
Caches:
I'm seeing changes on the fly with fonts (and the display on websites), if I try and move fonts that had warnings like Arial styles or Helvetica styles back to my User Directory, so I'm guessing that Font Caching isn't affected by this.
If anyone is going to suggest that I deal with the font cache (since I've read several questions on this topic already), I'd appreciate some explanation about WHY I would need to address font caches and HOW they might be affected in respect to your suggestion and the problems I'm having.
Additional Information:
I use a MacBook, Mac OS X 10.6
~ If there's some other information that you may need from me, then please ask away... I need to figure this out, and Font Book is driving me crazy!!!Yes hindsight is 20/20. I realize now that I should not have allowed FB to do what it asked. (But that's a moot point now).
Having a large number of fonts is something I've always had for design purposes. I never had issues with fonts on a PC, and didn't expect these sorts of problems on a Mac. And how is someone suppose to know NOT to trust a pre-installed program that's suppose to MANAGE your fonts???
I don't touch the system fonts. I am well aware that they can't be deleted, nor do I add any fonts to that directory.
I agree... I need to narrow down the issue. That was the whole point of posting this!
I do keep backups of my system and files. I have considered just replacing the font folders with what I had before, but it just brings me back to where I had all the warnings, errors and duplicates... And I'm not entirely sure if and how that could affect the font caches, and if I would need to then address those. I've been researching this quite a bit, but so far, all I've found is complaints or questions from people with similar problems. For whatever reason, very few people seem to want to offer help with this kind of problem (but I thank you for at least trying)...
With Dreamweaver, its not quite that simple. If it was, then I wouldn't need the help. Even if we disregard the issue I have with Dreamweaver, the problem also exists on some websites, webmail, etc. Websites (and Dreamweaver) use standard font families and display their fonts from YOUR installed fonts. The font problems I'm have online are not missing fonts, they are just not the same font in size or appearance that they were before (and no, my webmail, and these websites didn't change. I had someone give me some screenshots to confirm). But I can't figure out exactly where the problem is, because it appears that I DO have the standard fonts. It could be that FB removed a version that was better than what was left behind, or it could be something else.... I have no idea anymore. I'm just getting more frustrated. -
Fonts showing up in Font Book, but not in other apps
This morning, while rummaging through Font Book for something new to use, I discovered that some of my (large) collection of fonts did not show up in various programs... meaning I never think of using them unless I'm actually rummaging through Font Book.
I got onto the Apple support forums and looked at why this might be. I discovered that some of my fonts, for various reasons, were only in the "User" folder, while some that were listed in "All Fonts" were NOT showing up in the User folder. Cleaning this up seemed like a good place to start. I quit Font Book and all other programs, went to /Library/Fonts and ~/Library/Fonts, and moved all the fonts in the User folder into the All folder, as suggested on some answers here. (In addition I changed my Font Book prefs so that new additions in the future will not go to the User folder, but to the main folder and be usable to all.)
Then, also following answers here,
—I did a Safe Mode reboot
—rebooted again out of Safe Mode
—removed font cache files through Terminal
—and finally checked Font Book.
The screen shot above shows that all fonts are under "All Fonts" now, instead of some showing up only under All and some, oddly, only under User, as it was before I started the cleanup. Nice and neat. There is no User folder anymore, and I assume that is because it has no contents—User gets what All gets. Seemed like everything worked.
So I opened one of the programs I use to take notes (Microsoft Entourage), just for a quick check...
... and discovered that some fonts which *have* always been usable, are now not showing up. (On the plus side, however, some of those fonts which had been hidden to me—ones that I discovered in my morning rummage—are showing up, so half of what I was aiming for is working.)
I read a few more support forum posts, and saw that some folks have success when they remove the fontbook .plist. So I did this as well, and checked everything again.
Font Book itself is still nice and neat, and appears to be complete, but Entourage and TextEdit, which I chose to be representatives of how this font cleanup is working in real programs, still do not show all my fonts. And stranger still, though most of their problems are the same, each of the programs also has different fonts which are or aren't showing up!! For instance: Aviano Slab, shown highlighted in the screenshot, isn't visible in either program, but Aviano Flare, right above it, is visible/usable in TextEdit but not visible/not usable in Entourage.
Now, to be clear, as far as I know all of my typefaces are currently showing up in Font Book, and about 95% of my fonts are visible in both Entourage and Text Edit, even though the 5% that's problematic is partially the same/ partially different in each. I hope I'm not going to have to open every single program I own to keep checking for variations—hopefully knowing that there *are* variations between programs will help someone to give me a suggestion.
If the 5% that don't work were the exact same, I was going to assume Mac voodoo. My lame workaround was going to be, to manually check my font folder against one program or the other, and copy every font that doesn't show up, back into the User folder. It would take quite a while, and there would be two copies, but at least the ones that are not visible to my programs would (hopefully?) be visible again.
But the ones that don't show up and therefore can't be used are not all the same. So this indicates worse voodoo, some sort of font management issue that I don't get, and it probably means I'd be at this check-and-copy thing forever with each and every program I use. Or, I could waste a lot of disk space, and copy all fonts to User. Ugh.
So I'm hoping that by laying out everything I *have* already tried this morning, someone will be able to spot a step I missed that will help me get Font Book to wrangle these darned typefaces better.
If Font Book *thinks* all fonts are now available to all users, how can I get my programs to agree—and get my programs also to "see" and let me use all of my fonts?
MacBook Pro, Mac OS X (10.7.5)
Font Book version 3Okay!
So, should anyone else ever find themselves with this weird problem, here's what the rest of my day looked like—and yes, I did at last get the problems solved.
First I printed out a list of all my fonts (in the /Library/Fonts folder). Very long. Then I skimmed through the two programs standing in, hopefully, for every program, to try and see if something the problem fonts have in common would jump out at me.
One thing did: all of the "problem" fonts in TextEdit (the ones that didn't show up, in other words) were from a period when one of the type companies I use was automatically installing to a subfolder within the font folder (named with their company's name). Though TextEdit "sees" all the fonts in the Microsoft subfolder, apparently it can't handle other subfolders. So I removed all of these fonts from the company subfolder to the main /Fonts folder, and solved one problem. This problem, oddly, must have been there all along, but who uses a ton of fonts in TextEdit? So I didn't notice the problem until I was troubleshooting today, and thinking that was a nice neutral program to test things in.
But it did nothing for the problem in Entourage, which is where I began my day—even though *some* of Entourage's problem fonts were also in that subfolder, most were not, and the ones that were in that subfolder were still not made visible to Entourage by moving them out of it. So then I scrubbed the long, long list of fonts, looking for all the ones that were not visible in Entourage. Blech. That took a while.
When I got my complete list of missing fonts, I went back to Font Book and validated all of those fonts. I discovered that all but one, share one tiny problem: the "'name' table structure" error. (The final font did have a minor error in validation, but not that error.)
Now I didn't make a list early this morning, so I can't be sure that every one of these fonts was among the ones that started my attempt to clean up and make things right, but I'm assuming they are. I suppose it's possible that during the things I tried to fix the mess today, that one or two fonts actually started working on their own, but probably this list would be the same as one I could have made in the morning, back when I was young and innocent and thought I wouldn't need lists because it was all going to work with ease.
Before I got too excited, I then stopped and validated all the fonts I have. I wanted to make sure that this wasn't an error tons of fonts of mine have, in which case I had not located the problem. But in fact, only the typefaces I couldn't see in Entourage had this error. So I went back to the www to search for what to do about this error.
And in case anyone else needs to replicate my success, this is the site with the fix that worked for me on it:
http://www.iwebss.com/tech/540-fixing-fonts-with-validation-errors-on-mac
Skip down to where it says "Quick Instructions." Download the program suggested there, and do *exactly* what it says under Quick Instructions and no more (and please, make a folder with copies of any otfs or ttfs you need to do this with before you try the fix, in case it doesn't work for you as it did for me and you need to back up to the old versions).
One note: in those instructions, he doesn't mention that after "Save As," the program may hang up and give you a nasty message about access—just go to the Finder and do a Force Quit, no need to report, open the program again, and carry on. You haven't harmed the font or the program, and it does save before hanging up, so you can just go on to the next font in your list. For some miraculous reason, doing this does repair the "'name' table structure" error (and the error that the one odd font had as well!), and when I reopened Font Book, Entourage, and just for good measure, TextEdit, all of the fonts which had been plaguing me were perfectly visible and absolutely functional.
Thank you, Kurt, for your good ideas here and elsewhere on these forums. You were of great help to me today even before your answered this question. Though I was so deep in troubleshooting that I didn't get back to see your latest reply, I appreciate your taking the time to try to guess at this very odd hiccup.
Why this error bothers some programs and not others... why it's so easy to fix, with a simple program that you purposely use to make absolutely no changes... who knows. But check your subfolders first, and if that's not the problem, try validating fonts and see if the "'name' table structure" error is at the root of your problems. Perhaps this will work for others. -
Font Book is showing fonts in non-english characters
Been installing my old fonts and the like to Font Book on Mountain Lion but I seem to be running into a small issue as I install.
Besides the fact that I'm getting the 'A-image' for some of the fonts, a fair few of the fonts themselves also seem to be showing up in what looks to be some sort of alternate language?
I uploaded a few examples here as well to help explain the problem I'm running into.
This is actually a fairly new computer, only a few days old, so there's hasn't been a lot that I've done that I could assume would be doing this.
Any help or suggestions would be great, thank you in advance for any assistance you can provide!The first and third fonts are showing their Hebrew characters as a sample, the second one is showing its Thai characters. The 4th one is showing a character from the Apple Last Resort Font, which indicates a problem accessing the proper character.
I don't know why Fontbook does this, but I haven't seen any reports so far that it affects the usability of the fonts in question in any way. Does it for you? -
Font Book and duplicates. Strange Behaviour?
Hello,
I’d like to ask a question about Font Book and font duplicates.
Here is the situation. I’ve just installed Microsoft Office 2008 on a MacBook Pro (13’) running Snow Leopard (10.6.8). After the installation is complete and all of the Office updates are installed, I went to Font Book to check for issues. Surely enough, there were font duplicates.
In all cases, the fonts installed by MS Office (/Library/Fonts/Microsoft/) are older than the Snow Leopard system fonts (/Library/Fonts/). However, when in Font Book I Ctrl-click to “Resolve Duplicates”, what Font Book then does seems counter-intuitive, to say the least: it actually disables the newer Snow Leopard system fonts and leaves the older versions of these fonts installed by Microsoft enabled. No matter what I do, I can’t get Font Book to leave the newer system fonts enabled and disable the older Microsoft fonts.
This seems wrong to me and a source of potential problems. For example, won’t disabling fonts in the system folder and activating older fonts in the Microsoft folder cause future problems for the OS X system?
Am I missing something here? Is this normal? Any help would be greatly appreciated.
Regards,
StephenThanks, 'noondaywitch', for your quick and helpful reply.
Indeed, Ctrl-clicking on the individual font families, and then also on the individual styles of each font family (regular, bold, italic, etc.), one by one, seems to do the trick.
I went through them individually, and there seems to be no rhyme or reason to Font Book’s logic if you unleash it on the whole lot at once. In this case, unless I actually checked each style of each individual font family, it would appear that Font Book sometimes left older versions of a font activated, while disabling newer ones. To me at least, this seems bizarre. But then again, I’m not Font Book...
Thanks also for the link.
Regards,
Stephen -
How do I get fonts in my font book to a place where I can use them?
I have some Hebrew fonts in my font book but I don't know how to make them useable. I don't even know how to ask 'help' how to get them out. Meanwhile the Japanese fonts and the Chinese fonts are readily available.
I have a similar problem except I can't use any other fonts other than roman characters- all I want is to type in simplified chinese.
As with any other language, and just explained above for Hebrew, you go to system prefs/international/input menu and check the box for the simplified chinese input method you want to use, plus the box for Show Input Menu in Finder. Then in the "flag" menu at the top right of the Finder you select Chinese and type.
For full info on the various SC IM's, see the HELP in OS X or this site:
http://www.yale.edu/chinesemac/pages/osx5.html#start
If you have any questions, just ask again. -
InDesign CS5.5 doesn't show the fonts in Font Book
I recently upgraded to CS5.5 Premium at the same time as I upgraded to OS X Snow Leopard (10.6.8).
While I am asking this question about InDesign, all programs in the package (Illustrator, etc.) seem to have the same problem:
They don't recognise the fonts I have already installed in Font Book – TT, OT, or whatever type.
Has anyone else come across this issue?
In InDesign the only way round it seems to be to add the fonts I need to InDesign's fonts folder. But that doesn't change anything for Illustrator.
I hope someone can help.You don't really install fonts IN Font Book. You just use Font Book to place new fonts in one of two locations on your Mac. If you look at Collections in the upper left corner of the Font Book screen you should see one called User and one called Computer. These are really just references to:
Users > [yourname] > Library > Fonts
and
[computername] > Library > Fonts
Look in those two folders and see if the fonts are there.
All applications on your computer should show those fonts in their font menus. Do the fonts show up in other applications like TextEdit or Word?
BTW, there is the possibility you could have had problems with your 10.6.8 install. You might try running the 10.6.8 Update Combo as described in this article:
Mac OS X 10.6.8 Suffers Printing and Audio Problems -
Font Book: Installed postscript Fonts don't always appear in Font Book list
Greetings,
I was helping a user the other day with Font Book. I was showing him how to add/enable fonts into Font Book when I noticed a problem I had never seen before. Before I get started, the fonts in question are from the Adobe 7 Font Folio library. There were newly installed by me from the original disk, and known not to be corrupt. I also know that that Postscript fonts are an accepted font format in Tiger.
That said, when adding.installing a particular font using Font Book, it would not "Appear" in the Font Book" list of fonts. I would attemp to, again add/enable the font (by selecting it from the Adobe Library) and still it would not appear in the Font Book list with the other installed fonts. This would happen to any font that I tried to install. Once this happenend to a specific font, I could no longer get that specific font to install.
I removed the Font Book .plist - no luck. I also rebooted - no luck.
Obviously, no application was able to recognize any of the fonts that would not install.
It was as if Font Book would not recognize any font that I was trying to add/enable.
Could this be a corrupted cache issue, or .plist problem? Could this be a permissions related issue? What did work finally was to add the font to the "Computer" set, where it would be avaialbe to all users. But I could not get the font to install into the "User" set. Weird.
Also, What is the significance of these four fonts:
HelveLTMM
Helvetica LT MM
Times LT MM
TimesLTMM
These fonts above are part of the default package that is loaded into the /System/Library/Fonts
Is it safe to replace these with Postscript version from my Adobe 7 Font Folio collection?
I have read most of the font related tutorials and articals.
thanks,
Hairfarm
G4 Mac OS X (10.4.3)
G5 Mac OS X (10.3.6)where did
you get the information about pre-92 Adobe postscript
fonts being uncompatible?
Oh, sure, it's hard enough for me to remember things these days and now you want me to remember where I learned them from?? geez... [gone lookin' ... okay, back] It was, as I vaguely recalled, on the Adobe site, re troubleshooting in OS X, in a list of "do this to solve your problems": "Make sure that you are using the latest version of the font... If the font's creation date is prior to 1992, a new version of the font may be available." The only Type 1's that have given me any problems were, all three of them, older than 92, and in troubleshooting something here a few weeks ago, that turned out to be a problem for someone else, too.
But all of the Tiger font
research that I have done suggests that Adobe
Postscript fonts were acceptable.
Yes, well... Type 1's are supported. It seems that some older ones are a little funky (not in a design sense....)
Ideally, what fonts can be removed from Tiger from
the System/Libray/Fonts folder? I know that all four
of the MM's (Helvetica LTand Times LT), Lucida
Grande, Geneva, Keyboard, Last Resort, and Monoco
must stay, but what about the others?
You also need a real Helvetica - that is, not the MM version. You can replace the system's Helvetica with one of your own, but there must be an available Helvetica around at all times.
Then there's AquaKana (two of them, regular and bold). They're not on Apple's official "do not remove" list, but there's some anecdotal evidence of its being needed. It's "real" name begins with a period, so it doesn't appear in any menu, so it's not going to hurt anything if you leave it there.
In stripping down nonessential fonts, lots of people just remove everything from the Library/Fonts folder, but I think it's good to leave the basic most common web fonts available: Comic Sans, Georgia, Trebuchet, Verdana, Times New Roman. This keeps web pages looking the way they're supposed to - and they shouldn't conflict with anything that's being really designed!
This is assuming that the fonts
being used are not damaged and "Pass" Font Book's
validation test.
The assumption within that assumption is false: Font Book's validation is pretty iffy. I think the only reason we don't see it as REALLY iffy is because fonts, on the whole, are pretty solid in OS X (your current experience to the contrary). I've installed fonts (properly) that flew through the automatic-on-install validation but failed when I used the Validate Font command afterwards. I've had fonts that pass both the on-install and specific after-install validation but get a Bad Font warning dialog when being re-enabled after a disabling. (And I didn't use the font in between... ) Who knew Font Book did any validating when you re-enable fonts??
This is what I would do:
(Not necessarily in this order)
1. Trash Font Book .plist
2. Trash all Font Cache's from all three libraries
(System, Computer, and User folders)
3. Reboot
4. Delete problem fonts from User and Computer
Libraries and reinstall using Font Book.
Please tell me if this strategy is ill-advised, and
what the better course of action might be.
None of it is ill-advised. I would add starting up in Safe Mode to see if the problems exist there as part of the narrow-down-the-problem stage. Same goes for setting up a separate user account and see how things are behaving there. (Yikes... did you try that yet??)
In addition, there are some special things to do when it's Office apps having the problem, or something going on with Adobe's application fonts folder...
Also, Zaph Dingbats is acting up as well. I removed
the .dfont version that was in the system folder, and
replaced it with the Adobe Font Folio Postscript
version (ITC Zaph Dingbats) that I loaded into Font
Book User/Library/Fonts folder. Now that I think
about it, that specific font has been around for
along time, and may very well be pre-1992. Hmmm...
Can you further define "acting up" ? In addition to the ZD dfont from the system, I've been using/testing ITC ZD from Adobe with no problems. It's version 2.0 with copyright dates of 1985 through 1987.
A lot to respond to. My apologies.
No problem. You caught me on a night when I'm too tired for real work but not so far gone I can't do this (tho I'm soon on my way, bleary-eyed, to get a fix of Sudoku puzzles). -
Is Font Book Validation Bogus?
I have a folder of old Mac TrueType fonts that I have used from time to time with previous incarnations of the OS going back 6-7 years. I recently had a use for a couple of the Calligraphic fonts again and decided to install them in Tiger via the resident Font Book app. In Font Book's validation step, I got the red-circled X and a message that there were major errors and do not use this font on pain of instant death, or something like that. I tried every other TT font in the folder and got the same result. Finally, in the spirit of "everything is backed up and I can always reinstall the OS", I decided to drag the two fonts in question to my user/library/fonts folder and see what would happen. Nada, Nichts, Null, Nothing. I have been using the fonts for two weeks in several apps (I even made one the default font for Mailbox names in Mail) and there have been NO problems. Does Font Book speak with forked tongue? Perhaps some of you Gonzo Programmer types out there can enlighten me.
iMac 15, Daystar upgrade to 1.35 GHz Mac OS X (10.4.5)Despite the fact that I am not a gonzo programmer type...
Is FB validation bogus? Somewhat. You can install a font that is supposedly validated on installation, use the Validate Font on it after it's installed, and at that point it tells you there's a problem. Or use Validate File on an uninstalled font, it tells you it's no good, but if you just intall it, it passes muster. Maybe "erratic" is better than "bogus."
That said, I often run into problems with old fonts that get the red x/instant death message when I go ahead and use them. That is obviously not your experience.
For what it's worth, several old fonts of mine that were reported as damaged showed, in Finder's Get Info, that they were set to open with something other than Font Book. Selecting FB in the Open With menu fixed everything - they were no longer showing as damaged.
I'd be interested in knowing what your "damaged" fonts show in Get Info, and if they have the proper font icons. (Some of mine showed one icon on my PowerBook and a different one on my desk machine when I copied it there. Copied it back and forth, and the icon changed each time...) -
Font book or CS2 font problem?
I am using a mac Pro, running OS 10.4.11, w/ CS2. I am having a problem with either font book or CS2. Certain fonts are not viewing correctly when I use them in CS2 programs. I get a font error when I open the file, and when I try to fix the font by choosing the same name again, the font appears as another font entirely (in fact after I closed and reopened everything the font it substituted changed, and if I choose italic it changes fonts again). I do not know if the issue is with font book or CS2, but I have installed around 1500 fonts, and have had some other minor issues when I open files in Adobe programs, with fonts not showing up even though they are installed and enabled. I fix that problem by disabling the font and then re-enabling it and it then shows up in the font list.
So after all that, my question is what should I do? Should I reinstall CS2? Or is the problem more likely cause by font book?
ThanksFont Book is an inadequate font manager made by Apple for managing the few meger fonts Apple includes with the system.
FAP is a robust font manager made for professionals with thousands of fonts
Maybe you are looking for
-
My ipod touch 5th generation won't connect to itunes or my computer.
So i was syncing my ipod touch to itunes, however in the middle of the syncing itunes froze. So i closed itunes and now when i plug my ipod touch back in it wont recognize it or connect to my computer at all. And if i just plug my charger in, it'll p
-
Since I downloaded Firefox 4, I have not been able to save changes to my bookmarks (this includes both adding new bookmarks or deleting old bookmarks). When I make a change, the changes are not saved the next time I restart Firefox. After doing a Goo
-
How to put an new ipod to an existing itunes
Dear all, I got a new ipod nano and would like to sync. with my existing itunes. The ipod which was linked to it went lost.
-
I have plug and external scsi cd rom in my machine and i need to mount it but i am unable to found it in /dev. Where do I get it.
-
Hi SAP Experts, I need you help and illustrations to understand the difference between these two infotypes IT0008 and IT1005 and how it got linked so much, i have seen some tables T510A and T710A, they maintain levels and paygrades. Can any one expl