Font Book - attach notes to fonts?

Is there any way to attach a note to a font? for example, a font not otherwise notable that has a few remarkable characters, or unusual numbers.

So far no answers here. But I have found out that the free Linotype Font Explorer offers comments and labels, so I am going to try using it. It has more capabilities than Apple's FontBook.

Similar Messages

Font Book does not recognize fonts in /library/fonts

I just did an erase and install. I chose to install extra fonts into the system and this wierd problem just started yesterday. Font Book will not recognize the fonts in the /library/fonts folder. Font book will not even install additional fonts in this state. I restarted the computer and that seemed to fix the problem. But now it's back again. I think it happened after I woke the computer from sleep mode, however the problem does not appear everytime I wake the computer up. I noted the following entries in the system log that seem to coincide with the problem after waking the system.
(after the system is waked)
Jan 2 15:41:35 (name) crashdump[991]: configd crashed
Jan 2 15:41:36 (name) crashdump[991]: crash report written to: /Library/Logs/CrashReporter/configd.crash.log
Jan 2 15:41:36 (name) launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[981]: exited abnormally: Hangup
Jan 2 15:41:38 (name) kernel[0]: SIOCPROTOATTACH_IN6: en0 error=17
Jan 2 15:41:38 (name) configd[992]: LINKLOCAL: inet6attachinterface(en0) failed, File exists (17)
Jan 2 15:41:38 (name) kernel[0]: SIOCPROTOATTACH_IN6: fw0 error=17
This is the console entry I get when I attempt to install a font from /library/fonts when the Font Book is "blinded".
2006-01-02 17:20:48.784 Font Book[1480] Failed to deactivate container 34, with status -45.
2006-01-02 17:20:49.246 Font Book[1480] ATSFontActivateFromFileSpecification w/Validation options failed -120
2006-01-02 17:20:49.246 Font Book[1480] file://localhost/Users/~/Library/Fonts/Zapfino.dfont
2006-01-02 17:20:49.246 Font Book[1480] ATSFontActivateFromFileSpecification failed -120
2006-01-02 17:20:49.247 Font Book[1480] file://localhost/Users/~/Library/Fonts/Zapfino.dfont
Does anybody know what the problem is and how to fix it?

Well, I'm glad trashing the fonts cache fixed that problem. Font conflicts have been known to totally screw up things like MS Office. Whether or not it could screw up launchd, I don't know. But, if the problem doesn't resurface, then it definitely did.
However, I'd send a bug report on the launchd crash to Apple and include the crash report. Send bug reports and enhancement requests to Apple via its Bug Reporter system. Go to <https://connect.apple.com/MemberSite> and join the Apple Developer Connection (ADC)—it's free and available for all Mac users and gets you a look at some development software. Then, go to <https://bugreport.apple.com/>, click on the Login to the Apple BugReporter link (using your ADC username and password), and file your bug report/enhancement request. The nice thing with this procedure is that you get a response and a follow-up number; thus, starting a dialog with engineering. If your item isn't fixed with a new update, you can fire a follow-up on your original, via e-mail.

Font Book does not recognize some Postscript type 1 font files

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

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

How do I add new fonts I've downloaded to Microsoft Word? It's in my font book but not usable on MW., How do I add new fonts I've downloaded to Microsoft Word? It's in my font book but not usable on MW.

How do I add new fonts I've downloaded to Microsoft Word? It's in my font book but not usable on MW.,

Typical issue with Font Book.
Restart your Mac and immediately hold down the Shift key when you hear the startup chime to boot into Safe Mode. Keep holding the Shift key until you see a progress bar towards the bottom of the screen. You can let go of the Shift key at that point.
OS X asks you to log in (you will get this screen on a Safe Mode boot even if your Mac is set to automatically log in). Let the Mac finish booting to the desktop and then restart normally. This will clear Font Book's database and the cache files of the user account you logged into in Safe Mode.

2 fonts in Font Book do NOT appear in AW WP list

2 fonts in Font Book do NOT appear in AW WP list ( I have used them previously on an eMac and iMac)

Welcome to the forums!
Do you mean you don't know how to see any fonts at all? If that is the case, use the Font icon in the toolbar, or go to the Format menu, and in the Fonts submenu choose "Show Fonts" (or use the keyboard shortcut Command-T). Any of these methods will bring up the Font Panel.
If you mean that fonts do not show up in the Font Panel, be sure that the fonts themselves are turned on in Font Book.

Font Book Will Not Install New Fonts

I have purchased several new fonts that I need to use for an upcoming project. They are .ttf files. Whenever I try to install the fonts using Font Book, they do not install (no error messages or anything comes up) and it returns to the Font Book interface. I have restarted the app and restarted my macbook pro but I am still having the same problem. I've searched around but the only topics I could find regarding this were back in tiger. Any help?

Font Book is not a real font manager. It is not ready for prime time and may never be. I'd clear all settings from it and simply copy the fonts in question to your /Library/Fonts folder if you intend for them to be available to all users or to your <username>/Library/Fonts folder if you want only the user <username> to have access to them. That'll work.
If you feel that you must use a font manager, get a real font manager. Suitcase and Linotype's Font Explorer are real font managers.
I, personally, have more than a thousand fonts installed on my system and don't use a font manager. Especially I don't use Font Book. At best it's useless. At worst, it messes things up.

Font Book will not open...

When trying to open a font or open Font Book..
I keep getting the "Font Book Applictation quit unedpectedly" message.
I am unable to open it...
Any ideas?
-Jeremy-

Either Font Book's database is damaged, or you have damaged fonts. If it's the later, having damaged fonts will always in turn damage the database.
Follow the steps in Undoing Font Book. Note that you will lose any font collections you have created. Doing this will also clear the system's font cache files.
If after that Font Book dies again, then you have damaged fonts. To replace all fonts that came with OS X without reinstalling the entire OS, follow the last section in my article, Font Management in Mac OS X Tiger and Panther, to put all new copies of your fonts on the hard drive. Repeat the steps for Undoing Font Book.
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.

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)

Font Book automatically activates deactivated fonts

I've got a whole load of fonts in my (hard disk)>Library>Fonts folder, most of which I deactivated in Font Book as I use them very rarely.
But every time I reboot my Mac, Font Book reactivates all the fonts, which is a right royal pain in the backside!
Please can anyone suggest the best way to stop it doing this?
Blue Dalmation iMac Mac OS X (10.4.5) 600mHz processor, 1Gb RAM

Robin --
The fonts in your HD>Library>Fonts folder are put there by the System.
(Unless you purposefully put others in that location.)
There are several that have to be there for your computer to work well.
They are:
Courier.dfont
Geneva.dfont
Helvetica.dfont
Keyboard.dfont
LastResort.dfont
LucidaGrande.dfont
Monaco.dfont
I learned from terrible experience, that it's an excellent idea to leave
the System Fonts alone. There are some you can fool with, but I wouldn't do it again if my life depended on it. Fonts in the Users>Library>Fonts can be fooled with, but not the System fonts.
Here's a great FAQ on fonts in OS X
that should help you out.
http://discussions.apple.com/thread.jspa?messageID=607630&#607630

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.

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.

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.

Some fonts are in library fonts folder, but not in font book or in illustrator

imac/tiger/illustrator11
So I have some fonts that are in library>fonts but do not appear in font book or illustrator font list
also no fonts names listed in attributes, when you highlight font in the artwork, (but does list whether it is regular/bold!)
-also when I go about illustrator(11) it gives me info but locks program and have to force quit

Type 1 (PostScript) fonts require 2 files to make them work.
The FFIL files are screen fonts which load into the OS/programs in order to show up in the menus. They should show up as Font Suitcase in the KIND column of the finder. You will also need the corresponding LWFN file which is the postscript outline file. That will show up as Postscript Type 1 outline font in the KIND column of the finder. That is used to render the font on screen and output it.
OSX needs both of those in the same location in order to work correctly. Needing two pieces is just part of the problem. The names of the files are also different. The PostScript parts usually having abreviated names.
And it's more complex than that. One FFIL file actually may have many screen fonts inside it for the different variations of the font family. Then you will need to make sure you have separate LWFN files for all of those.
I know it's confusing. The 2-piece font just asks for problems. Unfortunately that is how Adobe invented them 20+ years ago.
OSX makes it harder by not letting you open the FFIL file to see what's inside. In OS 9 and earlier you could open the suitcases and add or remove screen fonts - even add unrelated fonts all to the same suitcase
Well I've rambled enough about Type one Fonts. I hope my first few paragraphs clear up some of it for you.

My Font Book is not working since installing Yosemite

I've got a Mac Pro (Early 2008). Since installing Yosemite my Font Book refuses to launch. Can anyone help?

I have tried all the suggestions posted on online forms to no avail.
Please describe in detail all you have attempted to do in order to resolve the issue in case there were things you missed.
I think as a loyal customer I deserve better than this....
I'm a loyal Chevy car owner and I am treated no differently than a first time Chevy owner. Apple is just like any other huge corporation, they treat all their customers the same. Doesn't matter if you're loyal or not.
Mac OS X (10.6)
Use Software Update to update your os and anything else that needs to be updated. You are seriously outdated for Snow Leopard.

Font Book - attach notes to fonts?

Similar Messages

Maybe you are looking for