Office Font Book Issues

I've read the other threads, and have tried most everything...
Reinstalled Office 2004 S&T Edition, Word, Excel, PPoint won't open. Entourage does. Font Book won't open - gives error message. Tried creating new user, same problem. Tried archive and install, got error message that it could not complete the archive and install. Any help would be appreciated!

I would re-post your question in either the OS X discussions, or on Microsoft's own newsgroups, as it's not really related to "Windows Compatibility."
http://discussions.apple.com/category.jspa?categoryID=160
http://www.microsoft.com/mac/community/community.aspx?pid=newsgroups
(12098)

Similar Messages

Font Book Issue

Hey everyone, This may well be a simple issue, but for the life of me i cant figure it out. Recently, i added new fonts to my font book and they seem to have done something to the pre-existing fonts. Whenever i get a permission pop-up, where i need to enter my username and password, like to install software, all of the letters are just one character, which i can't describe. Is there any way to fix this or do i need to bring the computer in for repair?

It sounds like you added one font too many. Check Fontbook to see if you now have any duplicate fonts, especially for Lucida Grande. There should just be one, located in System/Library/Fonts.

Font Book Issues Installing a font

I was recently given a font that doesn't seem to want to install in Font Book. At first I thought the files were corrupted but I tried installing the same font on my MacBook Pro and it worked fine. I have tried to add the font from the Font Book interface, tried dragging and dropping the files into Font Book, and tried double-clicking the file and installing it from the file window... Nothing seems to work.
I did uninstall Suitcase Fusion about 3 months ago, mostly because I really didn't need it anymore. At least not worth the headache it was giving me. But I haven't had any font issues after the uninstall til now. I followed Extensis' unstall directions to the T.
Anyways I am at a loss as to why this font won't install. Any ideas?
Thanks in advance.

From the sounds of it, 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 they will not load. That's not a problem with Font Book, Suitcase or other font manager. None of them, nor the system itself will load outline fonts from a Type 1 PostScript font without the matching suitcase of screen fonts present.

10.6.2 Font Book issues

I've been searching hi and low for another post that might have the same problems, but to no avail. After upgrading to Snow Leopard 10.6.2, the PostScript font issue I'd been experiencing (like many others) seemed to go away. About 2 weeks ago, however, suddenly some of my fonts were no longer working? At first they were still in Font Book (and enabled), but wouldn't show up in InDesign, Illustrator, Photoshop, etc. When I checked the font files in the Finder, the file size was zero K. Strange.
So I deleted the files (from the Finder via Font Book), and tried to import the fonts back into font book after copying them over from a backup server, however, when I copy the font files from the server to my Desktop, the files go from 8 K (on the server) to zero K on my Desktop. So, of course, Font Book can't recognize the files as valid font files and can not import the fonts. Strange. The zero K files show up in my Library (at zero K), but they don't show up in Font Book.
Thoughts?
Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB

I know I'm late to the party but wanted to share my experiences. First off, thank you all - this discussion helped me immensely!
I was forced to upgrade to 10.6.2 after my my old mac mini began dying. I had been running a beige G3/System 9 and a Mac mini/10.4 networked together. I had all of my fonts stored on the G3. As you know, Macs no longer speak AppleTalk, so I was unable to connect to my G3 to copy over the fonts. I finally connected using the server connection (go->connect to server). When I copied over my type 1 fonts, the suitcases all showed up, but I was unable to install them. Another thread mentioned Font Explorer. I tried that and it didn't work either. I couldn't understand why there was a problem; I had updated to 10.6.3 and everyone said that fixed the font issues. I spoke to Apple support and they didn't know what was happening. (Actually the first guy blamed it on third party software - the fonts - and said it wasn't their problem. ***?!?!?!?) The 2nd guy was helpful, but had to escalate it. I was waiting for a callback when I found this thread and went to check out my font folders. Yep - zero k. But they were ok on my G3. Then I saw the last post about not being able to store type 1 fonts on a Windows server because they'd lose information. So I began wondering if having to connect to my G3 as a server affected the transfer of the fonts. Since my CD burner was down on the G3, I had to go back to port them over to my old dying mini on the AppleTalk network and then transfer them using target disk mode. Bingo. That was it. All fonts safe and sound. I'm sure this was a rare problem, but it's so bizarre that I had to share in case someone else can use my experience!

Font Book Issues

I installed some fonts and now have 1148 installed, many of which I wish to remove. However, Font Book 3.0 freezes on loading so I am unable to proceed. Your assistance is much appreciated. I am running OSX 10.7.4.

Hi ali,
Not sure if you know this, but FontBook from Lemkesoft is a font catalogue printing utility, not a font manager. When I first started reading Dimaxum's post, I also assumed he was talking about Apple's Font Book.
Anyway, FontBook (no space in the name) has been around for a long time. Back even before OS X. It is confusing when referencing these two apps. A person has to specify which one they're talking about.

Font Book - Office Issue

In the process of designing a bookcover I downloaded and installed several fonts via Font Book; however, these fonts are not 'recognized' by any MS Office app (e.g. Word, PowerPoint). What am I missing?
Thanks,
Chris

A better font manager probably. Have a read of Kurt Lang's advice in this recent thread;
https://discussions.apple.com/message/16132387#16132387

HT2509 Font Book vs Mountain Lion issue

Font Book keeps crashing as soon as it loads now that I have installed Mountain Lion. Is there a Font Book update that I need? I currently have Font Book 4.1
Using a 27" iMac 2.7 GHz Intel Core i5 with wireless keyboard. Don't seem to be able to do a Safe Reboot either.

You were right; corrupt fonts. Reloaded all fonts but did not validate any with issues. Seems to be fine now.
Until I need them again, of course. Which, most probably, will be in the near future.
Thanks for your help. I will persevere with Mountain Lion until something else goes haywire. Not impressed so far.

Font Book - duplicates & issues

My first issue is to do with duplicated fonts - which ones to leave active and which to close (or remove?).
First there is OSX - lots of lovely fonts, no problem.
Then we install Classic - some fonts duplicated, what to do?
Then we install applications - yet more duplicates arrive, which to turn off (or remove?).
Then I start to put in my own fonts and the fun really begins - I use a lot of Helvetica Neue and Gill Sans, but much larger families than come with OSX. How do I resolve these duplicates? If I have to keep the original system fonts does this mean I will always have to use and output a mixture of system + my families for the same font? This would not be good practice.
And now onto using Font Book...
I've tried various things like resolving duplicates (which ones get resolved?) and turning off whole libraries but most things I do seem to undo themselves pretty soon and I'm back to square one. Can I turn off a whole collection, then turn a few fonts on from within it? Having done this, the collection shows grey/off but all the fonts seem to be on.
All help very appreciated - please be gentle(!) - after years of DTP on OS9 I'm finding OSX really horrible. Many thanks all.
G5 2ghz dual Mac OS X (10.4.4)

Hi bogperson,
First, read through my FAQ/tip on fonts in OS X that ScotMij has kindly linked to. That may help you understand where fonts are and where they are active from in OS X. It will also help you get fonts on your OS X system down to the minimum which goes a long ways in avoiding font conflicts.
While Apple has brought Font Book a long ways in two or so years, it is still far behind the ease of use of third party font managers such as Suitcase Fusion and Font Agent Pro. Since you are in DTP and likely turn fonts on and off many times a week, you'd be much better off with one of these font managers.
To use your (I'm assuming PostScript) versions of Helvetica, remove the .dfont versions from the /System/Library/Fonts/ folder. You'll need to enter your password to delete them. Then always keep your PS version active by placing them in the /Library/Fonts/ folder and just leaving them there. OS X requires Helvetica for some of its applications, but it doesn't have to be the supplied .dfont version.
With the OS 9 (Classic) folder, there are some conflicts/duplicates that cannot be removed. And those are the four required fonts for OS 9, which are listed in my FAQ. All other fonts in the OS 9 /System Folder/Fonts/ folder can be removed. Don't be concerned that Font Book lists those four fonts as being in conflict with OS X's versions. Somehow, Apple made it work out so that they live peacefully together at the same time.
Personally, I run my system exactly as listed in my FAQ. All other fonts I activate are through Suitcase Fusion. I have always preferred Suitcase since it activates fonts for both OS 9 and X without copying or moving them anywhere. The only exception are OS X's .dfonts, which OS 9 cannot read in any way.
OS X is very daunting at first after years of OS 9 and earlier. There just seems to be so many files and folders. But after a while, it gets just as easy once you learn where things are. That, and you learn that the you never need to even look in the vast majority of folders.

Font book crashes on launch, can't use MS Office

Hi there,
I have a problem which started with MS office not opening. As soon as I tried to open a Word document, it would close saying that it has encountered a problem and needs to close. After a spot of googling I discovered that this might be a problem with a corrupted font, and sure enough fontbook wont open either!
When I try to open fontbook, it says that it has closed unexpectedly. Unfortunately, all this happened the day before I was due to hand in a 6,000 word project for my MSc which I could suddenly not access to print off... needless to say that after 4 years of trouble-free (ish) Mac ownership I was more than slightly hacked off.
Anyway I decided to create a new user account to test if the problem happened in there as well, and luckily everything was fine and I was able to print the document, but font book and Office still wont open in my regular user account.
Can anyone help?
Thanks in advance

Does Font Book still not open? If so, then you probably have some damaged fonts. Though it could also be an OS problem. But it's easier to start with the fonts, so try this.
At the bottom of my article, Font Management in OS X, you'll find instructions to reinstall all of the fonts that come with OS X.
Close all Office applications. Remove the following files. The tilde (~) indicates your home account.
~/Library/Caches/com.microsoft.browserfont.cache
~/Library/Preferences/Microsoft/Office Font Cache (11)
Go to the /Applications/Microsoft Office 2004/Office/Fonts/ folder. Copy all of the fonts in that folder to the /Library/Fonts/ folder, overwriting all of the existing fonts of the same name. The ones you want to replace may also be in your user account at ~/Library/Fonts/. You'll just have to look first.
If after that you still have problems, then it's more likely a problem with Office itself, or the OS.
The link, or one of the links above directs you to my personal web site. While the information is free, it does ask for a contribution. As such, I am required by Apple's rules for these discussions to include the following disclaimer.
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

I am having font issues with font book. It validates the font, yet it is not availabe in my software programs (Adobe or Microsoft). What can I do to use these fonts?

I am having font issues with font book. It validates the font, yet it is not availabe in my software programs (Adobe or Microsoft). What can I do to use these fonts?
I actually created these fonts with fontagrapher in 1998 and have been using them regularly ever since and now they are not available in InDesign. I really need to use them.

I found a page on Adobe, Troubleshoot fonts | Mac OS X
On PostScript type 1 fonts you need to copy/move the fonts to the correct font folder because Font Book doesn't copy them into the folder. Select the fonts double-click the fonts and Find in the font Book app and validate.
The correct font folder depends how you are set up. I am by myself so my font folder was MyHarddrive/Library/Fonts. I was using Suitcas fusion and the fonts are located in a different folder.
Most of the fonts have worked. Go to
http://helpx.adobe.com/x-productkb/global/troubleshoot-fonts-mac-os-x.html
This should help. Good Luck.

Font Book problems installing fonts - serious issues

I'm having problems installing fonts that I've been using for years. The Mac Mini Font Book says that there is serious problems with a lot of my fonts.
I don't want to install fonts if it is going to cause problems with the computer but don't understand why they won't work on mini but were fine on the emac.

gangof4 wrote:
Where can I purchase additional fonts?
Try typing "fonts" into Google. Have you really not done that?

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

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

Replacing Fonts Removed with Font Book

Font Book shows that several fonts that I frequently use, such as Times New Roman, have problems. If I remove them, where do I find replacements--the MS Office install disc, and do I have to reinstall the entire MS Office?

Start with Font Management in OS X
and if that doesn't solve your issues, see:
http://images.apple.com/pro/pdf/L311277AFontTTv4.pdf
http://www.creativetechs.com/tips/SVC-fonts/Fonts-2007-SVC.pdf
http://dl.extensis.com/downloads/SC/EN/P/FontsBest_Practices_inOSX.pdf
http://www.macworld.com/article/44942/2005/05/julyworkingmac.html

Office Font Book Issues

Similar Messages

Maybe you are looking for