Font Book - validating font

Hi Everyone
Using Font book to load fonts on a work project at home on my Macbook Pro laptop (intel core).
Have validated all but one family of fonts (highlights in Red serious errors...Do Not use these Fonts).
I was told by the Apple shop to just ignore it - but this is a proper set of fonts and nothing should be wrong.
Any Advice on this (or) a work around to help please.
My old laptop with Panther then Tiger would take any font - but so many things flag up with this new laptop.
thanks in advance!

There is no workaround. Get rid of the defective or incompatible fonts and see whether you can find equivalents that are compatible.

Similar Messages

  • Font Book validation problem when adding fonts

    I installed 10.6.2 last night and then turned the machine off as normal.
    This morning I start up and every action is followed by 10-30 seconds of spinning beachball action.
    The only process using up more than about 2% was fontworker which I've since found out is the startup font building/analysing/caching part of Font Book.
    I've read the suggestions on here about removing font caches, removing font libraries, etc. and have tried them all.
    The only way I've managed to get the system back up to 100% is to remove all fonts from my libraries (1500+ fonts) and run with just the system fonts installed.
    The problem I now have is that every time I try to add a font, the Font Book validation progress bar comes up, stays there for a minute or so per font and then says there's a serious error and it can't be validated and must not be used.
    I've tried it on lots of different fonts from lots of different sources (Adobe, Monotype, Microsoft, T22, Linotype, even some I've done myself with Fontographer/Fontlab) and the symptoms are identical.
    Any help happily received.

    Normally that would work, however I've already tried that - and to the other 2 font folders just in case - and I get no more fonts listed in my menus than I already had.
    Just for clarification I've tried them in:
    - Home/Library/Fonts (i.e. my user account folder)
    - /Library/Fonts (at top level)
    - /System/Library/Fonts (at top level)
    I've tried restarting with them in one folder at a time, then tried it again with them in all 3 folders.
    I should have followed the rule "If it ain't broke, don't try to fix it." as 10.6 and 10.6.1 were working fine, as was 10.5.

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

  • Please explain Font Book validation errors

    When using Font Book to validate fonts, it sometimes reports a variety of errors. Can anyone point me to something that explains the meaning and relative seriousness of the different errors that Font Book may report? Also, can anyone point me to information about which errors can be fixed and how?
    Thanks in advance.
    Daniel

    Let me ask this question a different way, since the answers I'm getting seem to misunderstand what I'm asking. Just to be clear, I'm not asking anything about whether Font Book is good or bad, about whether other applications are better, or whether it is okay to ignore Font Book's validation reports. Okay?
    I'd just like to know what the errors that Font Book reports mean. It seems crazy to me that Font Book would offer font validation, would run various tests and report whether those tests were passed or failed, and yet no information is available whatsoever about what it is actually testing. Does anyone know?

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

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

  • 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 Vs. Font Explorer

    Hi all I have for some time found a simple pleasure in downloading and collecting fonts, don't ask me why I find it relaxing, I don't know
    I was wondering what other people thought of LinoType's Font Explorer as an alternative to Apple's Font Book.
    Personally I find that Font Book can become tedious, especially when dealing with font duplicates.
    Recently i've discovered Font Explorer by LinoType, I find it so much easier to use and a lot better for font management.
    what are your thoughts?
    regards,
    Pee.

    I downloaded font explorer and it is great, better than suitcase as well. Very organized, the conflict feature is great as well, shows you all the duplicates and fonts that are either missing a printer or screen file and marks them in red. As you put your fonts into your user font folder just hit refresh in FE X and it sees them instantly, same with deleting them.

  • Font Book Automatic Font Activation

    Hello
    I have been happily using Automatic Font Activation from font book for quite long time. Today i noticed that feature absolutely died. Did not heal cleaning caches, restarting ATS Server via ATSUtil in Terminal command line. Simply feature stop to work and i did not really change anything.
    Please anyone could help me fix it?
    Do not suggest me any 3rd party apps i just liked it way it was before it stop working
    If that help, problem occurs only on my Mac Pro. All seem to work fine on my Macbook Pro

    You've done your trouble shooting!
    Try repairing disk permissions. It can fix a myriad of problems.
    Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and restart your Mac.
    If that doesn't help, try forcing background tasks...
    Mac OS X: How to force background maintenance tasks (logs and temporary items)

  • Font book disabling fonts

    I'm running Mavericks 10.9.2 and my Font Book application seems to randomly disable fonts. When I open the application to enable certain fonts, it disables them again anywhere from 5 minutes to a week later.
    There is no preference to keep all fonts enabled. Any suggestions? As a graphic designer, this is incredibly frustrating beacuse I need access to my font collection every single day!

    I have the same problem, Arial font is the one that affects me the most because it's used by a lot of websites. when arial is disabled in font book those websites look weird using other fonts.
    I'm also a graphic designer and I use Suitcase for my font management, I don't know if they might have compatibility issues thats causing the problem.
    Have you solved this?

  • Lion, Font Book & Adobe Font Folio

    Howdy All,
    I have a brand new Mac mini with Lion installed (of course) and I'm having a bear of a time loading the Adobe Font Folio. In general, I'm having a really hard time with Font Book on other Lion, late vintage, machines. I've tried every counter measure in my bag of tricks: boot in safe mode, Onyx cleaning, new user accounts, deleting plists, etc. At first I ignored the Font Book warnings, then I've heeded every one and not loaded the fonts. On my latest attempt, with a new user account account I have 444 fonts loaded, with the vast majority turned off, but Font Book hangs. I suppose I can always flatten the machine and start from scratch, but I'm just wondering if someone has an insight into the Lion/Font Book situation that I don't have. For the record, I have about 600 fonts running on about 30 Snow Leopard machines without any drama.
    Thanks in advance for ideas.

    Same here. My thread: https://discussions.apple.com/message/15995212#15995212
    I've had no replies. Have you looked at Activity Monitor while this is happening? check it out. I think i'm just going to go back to Leopard, don't know what else to do. Do you have an SSD in there?

  • Is Font Book a font management software?

    Is the built-in facility in Leopard OS "Font Book" a replacement for third party font management software (e.g. Suitcase)? Or is it still advisable to manage fonts using a third party software on a mac?

    Leopard's Font Book provides simple font management software. It's definitely improved from the Tiger version. It would probably meet the needs of someone who had a relatively small font collection without the need for frequently opening and closing fonts.
    For larger collections, or if you open and close fonts frequently, I'd recommend a more full-features application.
    A good and inexpensive eBook from TidBITS on Fonts in Leopard gives you a lot of info about how it works:
    http://www.takecontrolbooks.com/leopard-fonts.html

  • Font Book's font title show different style

    Hi mac people,
    I have create a font family, will publish to sell, but when i test it in the font book,
    in the information page, the title"ABC regular", use different style instead of my created style, other place have no problem.
    Why is this happening?
    How can I solve it?
    I create the fonts set by using a photo app to create the shape then use inkscape to convert the shape to sag file, then use font forge to create ttf file.
    Please help, really need answer soon!!!

    Hello and thank you for your reply.
    Yes, I used PostScript Type 1 fonts since MacOS 9 through MacOS X 10.5. I could see Cyrillic chars in Font Book (MacOS X 10.5 ver.), but they don't show in MacOS X 10.6 version of Font Book. Actually, I don't have any problem with using them in third party applications. It's just nice to preview a font before you choose to use on a page. Can't do it in 10.6. Other third party applications that allow preview a font, also don't show Cyrillic characters if a font is PostScript Type 1.
    Thanks.

  • Windows True Type font fine in Font Book but not in some apps

    I got a Windows True Type font from a guy having some issues with it when printing website on Windows XP and I thought I'd try the font on Mac OS X 10.4.4.
    It imports fine into Font Book and previews fine. When I opened up TextEdit the font can be seen in the list of fonts, but when one selects it changes to the Monaco font instead of the "real" font seen in Font Book.
    In Word the font don't show up at all but in Photoshop it seems to work fine.
    The font is validated fine according to Font Book.
    How come it behaves like this?

    Thanks for your reply.
    "OCR-A BT" is the name of the font.
    The origin I don't know about. I just got it from a guy I barely know.
    I know there can be various problems with fonts. Just thought it was interesting that Font Book validated and showed it fine, but still it didn't seem to be all healthy since it doesn't work in all app.

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

Maybe you are looking for