Missing Font, Font Book, and a Game?

I'm trying to run Wildlife Tycoon- Venture Africa on my 15" PB. It crashes soon after it is launched. I'm working with the developer and in WTVA's consol log a fatal fault is mentioned:
Error creating font [Arial (14)] -- it doesn't exist on this machine.
Fatal-ISV: (../engine/dgl/gFont.cc @ 39) Error, The Arial Font must always
be available!
A followup from their tech support indicates that the Arial font needed is "Arial regular" with a size of 14. I've found Font Book on my PB in the Applications folder. There appears to be 3 versions of Arial, but none are Arial regular.
I have no idea why this font is missing. Arial regular seems like a font my PB should have. My G5 apparently has it because the game launches on it. Has anyone heard of this issue before (missing fonts)?
Font Book is not very user friendly but it looks like Adding Arial regular is as simple as locating a copy of this font and dumping it into my font folder?
Can anyone offer any ideas where I can find this font onlline and if my premise about adding the font is correct? If not how do I get this font installed on my PB?
(I'm currently away from home on a trip so if I don't find this font online, I'm going to try to find it on my G5 and transfer it to my PB.)
Thanks!

Aha! Then you are missing the normal Arial face. Microsoft used to make a set of fonts available free called the "Web font kit", or something like that. It included Arial, among a bunch of other commonly used fonts. Unfortunately, they no long offer it.
But! They do have this one, which includes a copy of Arial identical to the one I listed. Download the link for "CoreFonts_update.bin" and you'll be set with a copy of Arial that should make the game happy.

Similar Messages

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,
Stephen

Thanks, '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

In Pages 5.2, some fonts "not available", yet present in Font Book and working in other apps

Using Pages 5.2, I open a document created in a previous version, and I get error messages about certain fonts within a font family being "not available" in OS X. However, these supposedly unavailable fonts are present in Font Book and work just fine in all other apps running on OS X. In fact, I still have the older version of Pages on my system, and it still finds the fonts without issue. The specific fonts troubling me at the moment are Myriad Pro Semibold It and Myriad Pro Cond. Pages 5.2 replaces them with Helvetica. I have wasted hours of time trying to resolve this problem, and I am at a total loss. What can I do?

Like so many other thing is is probably gone. Why not use Pages 09 that has about 100 features more than Pages 5. If you haven't deleted it it should still be in Applications/iWork 09 folder.

Font Book and ScalaSans

I am operating on OS X (10.3.9) using Quark primarily and Font Book.
I have had sporadic problems with my scala sans font family. Font book recognizes roman scala sans and scala sans italic, but not caps or bold. At first the problem would be solved by deleting the font and reloading it. After a few months, bold and caps stopped working completely. I've tried troubleshooting by deleting preferences, clearing cache, uploading original fonts, etc. I don't think the font is corrupt because its working on other machines operating on the same platform.
A friend suggested I try Linotype. When I switched over, problem solved. All fonts recognized. That is until I restarted my machine. Linotype stalled and I eventually had to force quit. Once I did, I got an error message saying that scala sans was unable to be located.
Just to see, I restarted, opened Font Book and then opened Linotype. Now I can use my fonts but both Linotype and Font Book have to be active. What does this mean?
Mac OS X (10.3.9)

Hi edmac,
In short, don't have more than one font manager on your system at a time. Most likely, Font Book is still interfering with the operation of your fonts. I would suggest putting the Font Book application on another disk for safe keeping and then deleting it from the Applications folder. That way, only Linotype's font manager is handling your fonts. Otherwise, when you double click a font to activate it, for instance, both Linotype and Font Book activate the font. Essentially, they get in each other's way.

Font Books and how to print them?

At home and at work, I deal with a growing library of fonts- about 57,00 at the moment. We use FontAgent Pro at work and I just got it up and running from Suitcase X1 at home. One thing we're looking to do is print out a comprehensive font book, and we need an application that is up to the task.
FontAgent's font compare is primitive, and the last application we used to print out a font book was theTypeBook on OS 9. It isn't even being developed anymore! Does anyone know of a decent application that's comprehensive and versatile? We're looking for typical A-Z, a-z, 0-9, symbols, and perhaps a word or sentence.
Any help is greatly appreciated!!
Power Mac G4/300 & Mac mini/1.42 Mac OS X (10.4.7)

Just to clarify, I have about 57,000 fonts currently. Also, I just migrated from Suitcase to FontAgent Pro at home.
Again, any help is appreciated! Thanks!

Font Book and Trash

First. when FB finds a serious issue, does it not load it?
Next. is it possible to extract a faulty version of a font that has several variations of that font inside.
In the "olden" days with ... was it called "Suitcase" or something like that... we could open a font file see what was inside and remove any variations.
If we can't do that with FB, what does anyone recommend. I have a faulty Bookman Bold, but in my Bookman folder all I see in Finder is:
Bookman
BookmBolSwa
BookmBolSwaIta
BookmCon
BookmOut
BookmOutSwa
So I'm guessing it lives inside "Bookman"
If I can't delete Bookman Bold, then my only alternative is to trash the entire font? Or at minimum Bookman?
This all started because I was reviewing my logs and see a number of failed validations. Oddly, I never turned these fonts on, so it seems like my Mac is checking all fonts whether installed or not? Here's an example:
May 11 12:24:09 stevens-mac-pro mdworker[326]: FontImporter: Validation failed - "/Volumes/New Pro/Users/ss/Documents/FONTS ARCHIVE/FFVortex/F.t1".
So I opened up Font Book and started temporarily loading fonts so I could find the faulty ones and then delete them off my drive. But I'm finding all fonts I remove from Font Book after analyzing them to end up in the Trash. But I guess it's just a copy?
Very confusing all this. Shouldn't be.
S

A previous discussion stated (I can't remember who):
A’s with boxes around them is always a sign of trouble with the main system font, Lucida Grande.
Quick possible fix is to remove ALL font cache files from the system to see if it's just bad cache data. For that, you need to use OnyX or other utility which will remove both system and user cache files. A Safe Mode boot won't work since it only removes cache data from the user account you do a safe
boot to. If after that the problem returns, then Lucida Grande itself is damaged and needs to be replaced.
To clear all remaining 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 and hit the return key:
sudo atsutil databases -remove
Terminal will then ask for you to enter your admin password. As you type, it will not show anything, so be sure to enter it correctly, then hit the return key.
This removes all font cache files. Both for the system and all user font cache files. After running the command, close Terminal and immediately restart your Mac.
If that doesn't do the trick, then reinstall the OS.

HT2509 I have installed a font from the internet into Font Book and saved it in my Fonts folder under my user library. How can I make it available in Word to type a document?

I have installed a font from the internet into Font Book and saved it in my Fonts folder under my user library. How can I make it available in Word to type a document?

Font Management in OS X

Help - Font Book and font Library doesn't work

I've just updated to a new iMac on Yosemite, and Font Book doesn't work. Neither does putting fonts into the "Library"
There is a range of fonts that ARE working that are already in either place, but some (that worked up until two days ago in my old Mac running OS 10.6.8) just won't work.
If I select the fonts in Font Book, Font Book doesn't load them. If I put them in the Library, they don't appear for use in any application.
As a designer, updating fonts is essential, and if this can't be fixed I'm in serious trouble! So any advice welcome!

We see posts like this here all the time. A person upgrades to a new OS, and Font Book suddenly stops working. Usually, the problem is that Font Book's database has been trashed by the upgrade with the very common symptoms you're seeing. You suddenly can't add fonts, and fonts Font Book says are open don't appear in some, or any apps.
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. Yosemite is a bit different. Whether it's a Safe Mode boot or a normal one, you get the same progress bar. It just takes longer to get to the desktop in Safe Mode. So hold the Shift key until you get to the desktop.
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.
If that alone doesn't do it (it should), then clear out all of the font cache data.
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 logged in user account. After running the command, close Terminal and immediately restart your Mac.

I can see a font from a previous project in a different program in Font Book and Illustrator is not finding the font when I open the file.

I am using Adobe Creative Cloud and have the new updates installed. The file was created in Artbook, but saved as a PDF. When Illustrator opens it says it does not recognize the variants (regular extended, light extended) of the main font (regular) which it does recognize. Any Clues on this front?
The font Skia-Regular_Extended is missing. Affected text will be displayed using a substitute font.
The font Skia-Regular_Light-Extended is missing. Affected text will be displayed using a substitute font.
To preserve appearance, some text has been outlined.

Have you searched the font menu for the name of the font?
In a PDF the font might also have been renamed.
If the font is there, but under a different name, you'll have to reapply it to the text.

Fonts show as missing in InDesign CS6 and now also InDesign CS5.5, but infact are there.

Company finally updated to CS6, large client's jobs all use Interstate. Yesterday would show as missing in CS6 but worked fine in CS5.5, Today show as missing in both versions but after exporting as various file types, the fonts are infact there. How does one get rid of the phony error, so I can see "Actual" errors? I handle 10 plus files a day from this client and sometimes they try to slip a new font by us.
For 16 months I've been loading and Activating through Font Book and have no problems at all until the CS6 install. I've removed and reinstalled fonts, I've tired all Library/fonts folders as well as Library/Application Support folders and nothing resolves this.
Any help or direction would be appreciated.
Thans
cidxtwo

The system requirements for stand-alone ID don't mention OpenGL at all. You might want to download a trial and see how it runs.
.idml does not include any link previews (that's one of the main reasons the file is so compact). Images that are showing up on the other end must be accessible so that ID can regenerate the previews.

Missing fonts in CS4 – how to install?

Hi all,
Apologies for asking a question that I've seen posted and answered, but I'm wondering if there is a simpler solution than the plug-in suggested.
I have lost a few of the fonts I regularly use. They appear in Font Book and are enabled, but they are not available in InDesign. The missing fonts are available to me in other programs (e.g Word) so they are definitely on the system.
I was given advice to check in Home > Library > Application Support > Adobe > InDesign > Fonts, but there is no folder called "InDesign" within the Adobe folder of that path, so I don't know if that was good advice.
Of course (always the way, isn't it?) I've noticed this problem one week out from my deadline to the printer, so would really appreciate resolving it quickly.
Thank you in advance,
Andrew

Well, if your goal is to make the problem go away without
understanding it, thus reducing the liklihood you'll understand the
cause and prevent it from recurring in the future...
"Sometimes they get sleepy" is an attitude that really bothers me at a
deep level. Programs shouldn't break. And when they do, we should make
the effort to understand why they do. And report those problems back
to the manufacturers, who should be given the opportunity to fix
them. Even if we think they won't.
Programs break for reasons. Sometimes complicated and tricky
reasons. Sometimes reasons we can't actually figure out. But sometimes
reasons that we can. And we need to take the effort to figure out
why. Or at least try to a reasonable effort.
It is our moral duty. Otherwise the programmers who author the
software will have no opportunity to fix the problems, and thousands
of user across this green earth will be forced to deal with the same
problems we deal with regularly, for years and years, all because no
one was willing to take the minimal effort to figure out what was
broken and why.
Don't lie down and say "oh, it just broken again, I accept that i have
to jump through this hoop to fix it periodically." That's just not the
way it should work, and it doesn't have to be that way.

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.

Font Book disables fonts every time I restart my computer

First, some info on my computer:
- OS X 10.9.3
- Adobe Creative Suite 5.5 version 7.5
- Office 2011 14.4.3
- Suitcase Fusion 5 16.2.0
As a graphic designer, I've accumulated thousands of fonts. In an attempt to clean this up, I recently purchased Suitcase Fusion 5. I transferred the fonts by going into Font Book and selecting "Restore Standard Fonts." I then took the Macintosh HD; Library; "Fonts (Removed)" folder and added those to Suitcase Fusion 5.
Then I went back, and added about five of the removed fonts back into Macintosh HD; Library; Fonts — just because they are fonts I use frequently — as well as the Microsoft folder of fonts.
Now, for some reason, every time I start my computer (I shut down every night before leaving my office) about half of the Microsoft fonts are disabled by font book. The next day I enable them and everything works well and they all show up in both my Adobe and Office programs, but I'd really rather not play that game every morning. Again, almost all of the fonts being disabled are in the Macintosh HD; Library; Fonts; Microsoft folder, but only until the Ms or so, after which point they all show up as enabled and work just fine. And then there are a couple of outliers I've marked with an asterisk, that are just in the typical Macintosh HD; Library; Fonts folder that are also being disabled, the most confusing one being ThirstyRoughTextures.ttf, because the rest of the Thirsty Rough family is working just fine. (This single Thirsty Rough file is the only of the five-or-so fonts that I added back into my library after restoring it to standard fonts that is acting up. The others show up in all programs just fine.)
Anyhow, does anyone know why this might be happening, or how to resolve the issue? Any input would be great, thanks!
Fonts being disabled:
Adabi MT Condensed Extra Bold
Adabi MT Condensed Light
*Arial.ttf (in Fonts folder)
Arial.ttf (in Microsoft folder)
Baskerville Old Face
Batang.ttf
Bauhaus 93
Bell MT
Bernard MT Condensed
Book Antiqua
Bookman Old Style
Bookshelf Symbol 7.ttf
Braggadocio
Britannic Bold
*Brush Script.ttf (in Fonts folder)
Brush Script.ttf (in Microsoft folder)
Calibri.ttf (Bold Italic, Bold, Italic and Calibril.ttf)
Calisto MT
Cambria.ttf (Bold Italic, Bold, Italic)
Cambria Math.ttf
Candara.ttf (Bold Italic, Bold, Italic)
Century
Century Gothic
Century Schoolbook
Colonna
Consolas.ttf (Bold Italic, Bold, Italic)
Constantia.ttf (Bold Italic, Bold, Italic)
Copperplate Gothic Bold
Copperplate Gothic Light
Corbel.ttf (Bold Italic, Bold, Italic)
Curlz MT
Desdemona
Edwardian Script ITC
Engravers MT
Eurostile
Footlight Light
Franklin Gothic Book.ttf (Italic)
Franklin Gothic Medium.ttf (Italic)
Gabriola.ttf
Garamond
Gill Sans MT.ttf (Bold Italic, Bold, Italic)
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
Lucid Fax
Lucida Handwriting
Lucida Sans
Lucida Sans Typewriter
Lucida Sans Unicode
Marlett.ttf
Matura Script Capitals
Meiryo.ttf (Bold Italic, Bold, Italic)
himalaya.ttf
MingLiU-ExtB.ttf
*ThirstyRoughTextures.otf

I'm fed up with Font Book and ready to remove it.
Just to keep it easily handy, put the Font Book app on an external drive. All other supporting system files for it will still be on the drive, so using it again rather than a third party font manager is as simple as copying FB back into the Applications folder.
It is essential after deleting Font Book to follow the steps in my article to remove the abandoned Font Book database. Even with the main Font Book app removed from the drive, if the database exists, OS X will keep trying to read and use it, and it will interfere with all other font managers.
which seemingly only activates fonts once I open up that extension
Those are extension panels Suitcase adds to apps they've written them for so you don't have to go to the main interface in order to turn fonts on or off. It's a convenience thing to speed up access to your font sets.
what will happen to programs like Microsoft Office that aren't compatible with Fusion?
If you use a panel in the Adobe apps to turn any fonts on or off, all apps system wide will see the changes in available fonts since that's how it works with any manager. Or, you can launch the main Suitcase interface to do the same thing.
MS Office has an annoying quirk I haven't seen with any other app. It will not pay attention to any fonts you've activated or deactivated after Word has been launched. That's not a Suitcase issue, it's any font manager. Office simply does not keep tabs on available fonts while in use. To see fonts you've activated after Word is already running, you have to quit Word and relaunch it. Same with turning fonts off. Doesn't matter that they're not available any more. If they were when you launched Word, they'll continue to show in the list. Attempting to use one of course doesn't work. It types in Arial, or something, but not what you chose since it can't.
Is FontBook irrelevant and Office/any other program still just utilizes the actual HD/Library/Fonts folder without it?
When font management is working as it supposed to, all apps (save Office) will change the list of fonts you can use as you turn them on or off. It used to be, way back in Tiger, 10.4 (before 10.4.3) and earlier that any fonts in the System or main Library folder were available all the time with no way to control them, other than physically deleting fonts from those folders. This is still true of the System's Fonts folder.

Font Book does not recognize some Postscript type 1 font files

I am new to OS X and am trying to copy all of the fonts used under OS 9 (using Suitcase) to be available under OS X. I have copied all of my font folders into the correct location, but some of them do not appear in the font list within Font Book, and if I try to use the Add Fonts... menu to select these files they are grayed out.
The Finder shows all the problem fonts to be "PostScript Type 1 outline font", just as for the files which do work. Is there any reason some files may not work in the Font Book? Note that if the files are corrupted, I don't understand because they were (and still are) working fine under the Classic environment.
I'm not sure, but I don't think any of my TrueType files have similar problems. I have noticed that all of the PostScript Type 1 fonts which do work have an additional suitcase file in the folder, whereas the problem fonts do not. Does Font Book require a suitcase file to properly recognize and use the Type 1 files? I thought that the suitcase only contained the bitmapped fonts which are obsolete to OS X, but that's a guess...
Any help will be greatly appreciated.

Hi roxlankford,
Font Book can read PostScript fonts. But, as you've noted, you don't have the whole font. Type 1 PostScript fonts are a set. One file is a suitcase containing all of the low res bitmap screen fonts. The rest are the outline printer fonts. As an example, here's Adobe Garamond.
Adobe Garamond
AGarBol
AGarBolIta
AGarIta
AGarReg
AGarSem
AGarSemIta
The first file which I highlighted in green is the font suitcase of bitmap screen fonts. The rest are the outline printer fonts.
1) The files for a Type 1 PostScript font must have both the screen and printer fonts for a given set in order to work. They also must be in the same folder.
2) The suitcase of bitmap fonts will work alone, but output will be terrible since the system will print the fonts using the 72 dpi screen fonts in the suitcase if the outline portions are missing.
3) Having only the outline fonts will not work. You will get exactly what you are having problems with. You can see the fonts, but Font Book won't load them. That's not a problem with Font Book itself. No font manager will load outline fonts without the matching suitcase of screen fonts present.

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 3

Okay!
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.

Missing Font, Font Book, and a Game?

Similar Messages

Maybe you are looking for