Wrong name in font book

I imported a new font with font book. The font works in all applications but Font Book gave it the name "New". That is not the name of the font, how can I change the name?

Hi, NoahLD. Welcome to the Discussions.
If you install a font in Font Book and the font's name appears as "New" instead of the expected font name, this is because the creator of the font assigned "New" as the full internal font name. They may have been using a font-authoring tool that assigns "New" as the default name for new fonts they create, but they neglected to give the font a proper name.
You may want to report this to the font foundry from which you obtained the font.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

Similar Messages

  • Wrong name in email address and damaged index in address book

    I have experienced this problem for months now. I have a Mac Pro at the office and MacBook Pro at home. The address book is synced with .mac. At random I will receive emails and the mail program will attach the wrong name with the address ( John doe [email protected] will be displayed as mary smith [email protected] ) this also happens in mail I have sent and copied myself on. The incorrect name is usually one that exist in my address book. The second part of the problem which may be related is the index for both address books will get damaged. Every few days I have to discard the address book index file ( AddressBook-v22.abcddb ) which fixes the index issue for a few days. The computers nor the applications ever crash. I wonder if the .mac syncing could be key to both computers having index issues. Rebuilding the address index does not fix the wrong name issue. Both computers are 10.5.2. I feel there is some deeper corruption issue that rebuilding that one index file does not correct. I have also rebuilt all the mail boxes.

    SOLUTION: my ultimate solution to the address book confusing contact info in ichat, mail, etc. was to go to ~/Library/Application Support/AddressBook/ and delete the AddressBook-v22.abcddb file. back up your contacts first!!! but after you delete and relaunch, Address Book will rebuild using the info from the Metadata folder. worked like a charm.
    d

  • FrutigerLTStd-Bold Cn font has wrong name in file and not installing

    Just purchased FrutigerLTStd-Bold CN font.  The font file name is correct, but In the font window it says the name is "Frutiger LT Std 47 Light Cn" but the font shows up as the bold one.  Installed the font but it is not showing up in my font list.  Think there must be an error since the wrong name is thereI already have the light one, I need the bold font.  Was on hold with Chat for 30 minutes, they told me to call support.  Phone and said there was a 2 hour wait - my phone battery died before I was connected.  Help!

  • Font Book Names

    Hi,
    Is it possible to change the name of a font in Font Book?  I know how to change the name of the .ttf file but I can't seem to change the name of the font as it appears.
    Thanks

    It is possible, but only with font editors such as FontLab, FontForge, TTX, etc, or Apple's Font Tools. It's not something for inexperienced users.

  • Font Book crashes when trying to remove corrupt fonts

    I have recently upgraded to Snow Leopard and am having problems with my fonts.
    After installing some of my previously used fonts, some of them didn't pass validation. I don't mind removing them - I barely use 1% of the fonts I have, but when I run Font Validation in Font Book and then select all the corrupt files and click "Remove" - Font Book just gets stuck.
    Then I went by the list and removed MANUALLY all the invalid font files (the ones with the red cross sign).
    Then only the minor warnings remained , but even when I try to remove them with Font Book - it still crashes.
    It's ridiculous to remove them manually one by one, cause I have a huge collection of 1000s of fonts and there are more than 500 corrupt fonts there. I'm not using many fonts, but I want to keep my library up and working, so I want to get rid of everything that might cause problems...
    Any help?

    Hi Kurt
    Sorry, was busy, didn't answer for some time. Thanks - it helped me to run Font Book again and install new fonts, but Font Book is still causing me a lot of trouble - never had so much in Leopard - I'm frustrated, maybe you can help on those:
    After completely wiping clean all my fonts databases and folders etc. I've started loading back my Font libraries into Font Book. I don't copy fonts to any new folder, I just activate them from wherever they are without copying. First thing I noticed, is the amount of "corrupt" fonts has increased enormously - I have a couple of folders with alsmot all 400-500 fonts corrupt (yellow sign) with this error message: 'kern' table structure and contents. All of them with the same Error message.
    The next thing that happened, is that at some point Font Book has just deleted my new font libraries again without any notice. Then I installed them back again. It deleted them again (I think after a restart).
    Another bug is that Font Book always activates all the new fonts upon loading them, although I clearly runed off "Automatic fonts activation" in the Preferences. So every time I load a library I manually disable all of the fonts, and then enable only the ones I use.
    BUT! What happens next, is completely outrageous - when I launched FB next time, all my new font libraries where activated again! jezus - I had to go and disable them all and again activate the ones I need. This repeated several times, until I decided to delete the fontbook.plist prefs file from Preferences. I think it helped for now, but I'm not sure yet - will wait and see.
    Also there is a bug in FB, that when I install a new library, it always jumps my cursor into renaming the name of this library, and doesn't let me navigate the fonts with keyboard, unless I restart. This is an obvious bug.
    And the last thing that happened is that I cannot type my Baltic languages fonts anymore - the input of the keyboard is completely wrong. Those are TrueType fonts, and most of them worked perfectly in Leopard with InDesign. Now when I type the baltic letters in InDesign I see squares. But when I open Glyphs - I see all those letters and need to put them in manually from Glyphs panel. This is totally frustrating and I cannot work. But I will make a separate post about this issue.
    Thanks in advance for help...

  • Font Book Problem - Cannot see validated fonts in QuarkXpress

    We are trying to view the fonts that we have loaded into the font book from QuarkXpress. We can see the fonts in Adobe Design Premium apps (Photoshop, Illistrator, etc.) but not in Quark 7.3.1. The fonts validate fine in the book. We have tried removing Quark and reinstalling it. We have tried booting into safe mode to clear out the font cache. We have done a permissions repair, verified permissions manually for user accounts on the new font folder that is created, and removed and readded the fonts under the user and the computer sections of the font book. The fonts are ITC Kabel fonts. They work fine on another Mac that we are running Leopard on as well, but they are not visible through QuarkXpress from a different user account on this same Mac with the problem. The only thing that I can think of is a system reload using the restore settings option to keep her settings? Any ideas would be greatly appreciated! Thank you!

    Since we have reloaded Quark, I may try doing an install and archive on the OS. Maybe this will correct the problem?
    Maybe, it depends on what's wrong with Quark. It could be that the OS is indeed damaged and preventing Quark from operating properly. But it still could be another instance of Kabel being active. You searched for Kabel by name, but that's not how fonts actually work.
    Say you have a Word document on the desktop named "Budget report April 2008", but when you open it, the text is a grocery list. Fonts fall in that category. The name of a font you see on the desktop has nothing to do with the name that may show up in your programs. All fonts have an internal name. That's the one that gets reported to the system and is displayed in your applications.
    A suitcase of TrueType fonts can have up to 999 fonts stuffed in it. There's no telling what you'll get in your font lists until you activate the suitcase. So it's entirely possible you have Kabel as a font that's named something else on the desktop, or you have a suitcase of fonts active that has a font declaring itself as Kabel in it.
    Before going through an Archive and Install, create a new folder on the desktop. Move every font in the /Library/Fonts/ folder and the Fonts folder of your user account into the new folder. Use Font Finagler to clear the system's font cache files. Let the Mac restart.
    Now move just the font named Kabel back to the folder it was originally in. If it now shows up in Quark, you had a font conflict with something else you moved out of the Fonts fodlers.

  • Asian fonts display in font book but show as Western fonts in apps!

    Adobe apps still display Asian fonts as Western characters, even though I've changed language settings via the "international" control panel of System Preferences. Perhaps I have not done this correctly? I've restarted the machine after changes to Systems language prefs. Asian and other calligraphic fonts are all installed and display fine in Font Book. Is there a fix?

    As my aim is to access character sets without the
    need to change the language settings on my machine
    That's exactly what Character Palette does.
    think the ideal solution is to get a copy of
    Fontographer and copy all the decorative fonts and
    save them as standard fonts.
    A total waste of time in my view.
    True Futhark has several
    characters that stand for phonetics not compatible
    with plain roman alpha/qwerty keyboard use. I
    understand the same is true of other fonts-there are
    bound to be discrepancies.
    Most of the characters in the world are not compatible with qwerty keyboard use. That's why in general people don't use that method to produce them, or try to jigger fonts so they might be able to.
    Perhaps this is why so
    many characters come up as "?" even when inserted
    via the Finder's character palette?
    This may be because your app is set to Latin-1 or some other limited encoding. It should be set to UTF-8. Try Character Palette with TextEdit and you will not get any ?'s.
    Control+T does nothing in Adobe apps, as far as I can
    see. Apple+T brings up the Type palette but there is
    no "insert special character" option there.
    I got that wrong. The combo for Apple apps is Option + Apple + T. I don't know if that works in Adobe (don't use them myself).
    I did notice a wonderful
    Tibetan font that must be on my machine somewhere,
    though it does not show up in Font Book under "All
    Fonts"!
    These are part of the ST series of Chinese fonts. If you go to the Tibetan range in Character Palette you can see this and you can also input them in TextEdit or a UTF-8 doc. Or you can examine the contents of an ST font by putting Character Palette in glyph mode.
    I guess ideally, for graphics use, one should get the
    characters into a standard font file, as I suggest
    above, and then type away merrily qwerty-style.
    Some Asian scripts have thousands of characters. Using a qwerty keyboard to try to access a few of them from a recoded font is not something that anyone does as far as I know. They use a specialized Input Method or the Character Palette or a similar utility. Also unless you are truly transforming your output into graphics/photos, your input would be seen as qwerty on other machines.
    suppose these decorative fonts are available on the
    web somewhere, where those who sell them have gone to
    the trouble of transcribing the characters in to an
    'ordinary' font for you?
    Never seen such things myself.
    It seems a shame that Macs OSX can't grant you access
    to all these decorative fonts (indeed, to all
    installed fonts) in a more straight forward manner.
    The Character Palette is the most straightforward manner possible for accessing such scripts, if you do not want to switch keyboard layouts. All computer system use a similar mechanism. It even has a Favorites section where you can store characters you want to use frequently so you can avoiding looking them up each time. If you have some specific problems using it, I'd be glad to help, here or by email (click on my name for the address).
    Am I correct in these assumptions?
    No, I think all of them are wrong myself.

  • HT2509 i could use Burmese font with Zawgyi font in my previous iMac with Lion. Now I have a MacAir with Mountain Lion and i can not properly view Burmese fonts. Font book has 3 types of Burmese (myanmar) related fonts. Please help me to get proper displa

    I could read Burmese font with Zawgyi Font in my previous Mac Book with Lion. I have MacAir Retina display with MountainLion and could not read Burmese fonts. Font books have 3 fonts for Burmese font and all are enable. Please help

    pyoneaye wrote:
    Font books have 3 fonts for Burmese font and all are enable.
    What are the names of those fonts?  Have you downloaded and installed the special Zawgyi font?
    What is it exactly that you cannot read?  Can you provide the url?

  • Jabber Client CallerId displays wrong name

    Hi,
    I have a problem with the wrong name displaying in Jabber calls. This only occurs when John calls from his Jabber Client. There is always the CallerId of Sam showing up.
    Checked AD, Outlook contacts, CUCM & Webex configuration and found no errors.
    Then I generated a problem record in my Jabber for Windows client and found this in PROBLEM_FEEDBACK_Cisco_Jabber_17.49_01-08-2013\Contacts\PersonManager\PersonManagerForensics.txt:
    [1] <PersonResolver: 0D32AD90>
    Original record: <0D36E2B8>
    <Person: 0D36E370>
      <PersonRecord: 0D36E2B8> (Roster:[email protected])
      <PersonRecord: 09349160> Sam Sample (WebEx:[email protected])
      <PersonRecord: 0F10FE60> Doe, John (CallerID:+491234567890:Doe, John)
    In the other records there is only one name associated to one person. How did John number slip in here. And most interesting, how can I get rid of that entry? Where is it originated?
    Same Problem occurs at a customer site with a on premise deployment (CUPS). So it doesn't seem to be Webex related. Tried several Jabber versions from 9.1.3 to 9.2.3. Same behaviour.
    Any suggestions hints?
    Regards
    Andre

    I think I see what is going on, just not entirely sure why and how to prevent it yet.
    Look at the two records below, taken from the "PersonManagerForensics.txt" file generated once you report a problem through the Jabber application.
    That first contact is a personal contact in the users Outlook address book.
    The second contact is an employee.
    When the user calls the second contact in Jabber, the caller ID always shows up as first contact. Same thing happens if the second contact calls the user.
    The caller ID for the first contact is the same last 4 digits as the internal employees DID number. We use 4 digit dialing. Not really sure why the caller ID record for the first contact resolved to those last 4 digits of that one telephone number.
    Jabber issue....or Outlook issue???
    I'll open a TAC case.
    [2]
      Belinda Iberl (OutlookRecordSource:EF000000BC83CE4367E42B42B2EF336756A5DEA964E52100) [439-9380 OR 458-0170, 508-2938, 459-2220]
      (CallerID:2220:) [2220]
    3]
      Ryan Kooi (UDS:rkooi) [5204392220]
      (CallerID:5204392220:) [5204392220]

  • Fonts isn't showing up in Font Book but does in some apps

    I have a particular font that I use in a number of applications - Peignot. In fact it shows up in Text Edit, Mail, and Business Card Composer, to name a few. But it doesn't appear in Font Book, and more to the point, it doesn't show up in Word or any of the Adobe applications. It's clearly in my user Fonts folder and has been for months. I've only noticed the problem because I've tried to use this font in Illustrator. Can anyone tell me how this font can be present for some apps but not others? And is obviously installed but doesn't show up in Font Book?

    I just needed to reinstall a fresh version

  • My fonts that are installed in Font Book are not showing up in Microsoft Word. Can someone help me fix this problem?

    Hello!
    I am needing some help. I own a Mac Book Air with OS X 10.7.5. This computer belongs to the school district I teach for, so I do not have permission to do a huge wipe that would uninstall programs such as Word. When I first got my computer, I added all my fonts. I did this by putting them into a fonts folder. The fonts were not all showing up in Microsoft Word, so I was told to use Font Book. All of my fonts show up and are installed in Font Book; however, they do not show up in Word. I have restarted my computer. All the fonts are validated. I have tried almost everything I could think of after researching answers online. Another problem--my bullet points are messed up. When I click the bullet button, instead of an open circle it's an open rectangle. This doesn't concern me as much, but I thought it might help as a clue as to what is wrong. The fonts also do not show up in the Format > Font box.
    Also, I want to point out that my colleagues, using the exact same computer, network, etc, are able to download and use all the fonts. They have tried to fix mine, also.
    Any help is much appreciated! Maybe there is some way to wipe out my fonts and start clean?
    Thanks so much!

    There's a whole lot to read in your post, and frankly I have not read it all.
    Having said that, this troubleshooting guide should help:
    http://support.apple.com/kb/TS1538
    In particular, pay attention to the mobile device support sections near the bottom, assuming you have already done the items above it.

  • I am having trouble getting access to fonts on hard drive. In particular Helvetica Neue Black.  It seems that since HelveNeu.dfont is a system font Font Book  does not give me the option to activate HelveticaNeuBlack.

    We recently started using Font Book instead of Suitcase Fusion for our font management program.  We are unable to activate our postscript type 1 font (Helvetica Neue Black)  It seems since hel neu is a system dfont that Font Book thinks we already have it activated but HelvNeueBlack is not part of dfont.  So even though I have it in my fonts folder the font is grayed out and am unable to activate.  I might add that HelveBlack is also a problem.  I've read the article by Kurt Lang on Font Management.  I followed his directions on how to remove dfonts from system but caused more problems than it solved.  I would appreciate a certified way to handle these particular fonts.  Do I need to purchase the Open Type fonts to solve problem.

    What I did to fix was remove Helv Fractions that cleared up the problem.
    It's been quite a while since I've seen that one come up. When you mentioned that some of the type looked like jumbled fractions, that should have jogged my memory. Yes, Helvetica Fractions is long known to be a bad font. Delete it from the hard drive and never reinstall it.
    The HelvNeuBlack and HelvBlack fonts you sent are indeed creating conflicts. Here are screen shots of their internal names. HelvBlack first, and HelvNeuBlack second.
    In Helvetica Black, the menu name is just Helvetica, which leaves nowhere for the regular Helvetica font to display in your font lists. It also then creates a cross reference between the two fonts. It is also reporting two other different names to the OS for the same font. Helvetica Black, and Helvetica-Black. You can technically get away with doing that, but it's bad practice.
    Helvetica Neue Black is the same type of bad naming. The menu name is just Helvetica Neue, which leaves nowhere for the real Helvetica Neue to go in your menu lists. Then they rather oddly threw in Helvetica 95 Black for the full name, as opposed to HelveticaNeue-Black for the other two spots.
    Just some really sloppy work here by someone for what I would guess were Type 1 PostScript fonts converted to Mac legacy TrueType. If you don't have the software to fix the names, the only good suggestion is to throw these fonts out and purchase new ones from a vendor who builds fonts correctly. And while they're kind of pricey, that means either Adobe or Linotype.

  • Font Book won't remove font files

    I've been doing some testing with Font Book in hopes to replace Suitcase for font management. I've been testing on OS X 10.4.5 with Font Book 2.0.2.
    I have FB prefs setup with User as the default install location. Getting fonts installed works fine. To simplify for testing I'm just using one source folder with one family of fonts in it. So I drag the source folder into the FB window where I have created a collection called Temp.
    The font files are copied into ~/Library/Fonts, just as they should be, and are now available to the system. When I select the font family in FB and choose Remove Font, it disappears from FB, however the font files remain in ~/Library/Fonts.
    According to all documentation I've read, that is not the expected behavior. When Remove Fonts is used within FB, the font files should be moved to the trash.
    In addition, since the font files are being left in ~/Library/Fonts, if I try to add the same source folder back into FB, nothing happens, they just simply do not load. If I manually remove the lingering fonts from ~/Library/Fonts I am then able to add the source folder again.
    So it appears that FB is not functioning as advertised. I've confirmed this on two separate machines running 10.4.5 and also with one running 10.3.9.
    Any ideas what's up or am I missing something here?

    "When I select the font family in FB and choose Remove Font, it disappears from FB, however the font files remain in ~/Library/Fonts.
    Where are you selecting the font, from within the "All Fonts" collection, or within the "Temp" collection? If you've selected it from within your Temp collection, "Remove" only removes the font from the collection, not from your installed fonts. To remove the fonts from your installed fonts, you need to select them from within the All Fonts collection.
    I think what you might want to do rather than create a collection is to create an actual "Temporary" font library. In Font Book, select the All Fonts collection so that the focus is in the leftmost column and choose "New Library" from the action menu. Name it "Temporary" (or whatever else you'd like) and then hit enter. Notice it's listed above the dividing line which separates libraries on the top with collections on the bottom. Now, drag your folder of fonts from the Finder onto the "Temporary" library icon in Font Book. NOTE: A reference to the fonts will be added to Font Book; the fonts themselves are not copied but remain where they are in the Finder and are activated or deactivated from there. Now, whether you select the fonts from within the All Fonts library or the Temporary library, the "Remove" command will remove the fonts from Font Book. (Since the fonts remained in their original location, when they're removed from Font Book they're not moved to the Trash; rather, the reference to them is simply removed from Font Book).
    Hope this helps....
    Dual 2.7 GHz PowerPC G5 w/ 2.5 GB RAM   Mac OS X (10.4.6)  

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

  • 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

Maybe you are looking for

  • Connecting n95 with Sipgate VoIP to Talk Talk broa...

    I'm helping a friend set up her n95 on her talk talk broadband. the handset is successfully set up with sipgate and it works at my house, I've opened the ports on her Thompson Speedtouch 780 router as suggested by sipgate but still nothing. her TAlk

  • Cannot open pdf with safari

    I cannot open pdf with safari

  • How to import data from all excel worksheet ?

    hi I want to import data from excel worksheet. There is a fm ALSM_EXCEL_TO_INTERNAL_TABLE but it read data only from "actual" sheet. How can I    read data from all exel spread sheets ? krzys

  • Channel staggering

    Greetings i have a problem of too many airports and not enough channels. the building i am working with has 3 floors, and 20 rooms on each floor. each floor has cheap thin dry walls, therefor signal just passes right through. i have staggered the cha

  • POTS Sample gives exception

    I am trying to follow the POTS Sample code, specifically the PotsOrderConsumer class. This compiles but when invoked gives the following error: Exception creating order:153:Request parameter error:No legacy data found.  Namespace and Version need to