opkcertified.blogg.se

If it says the font is okay, right click on the font to both deactivate and delete it. Read - no junk.Īdd that font to Font Book and validate. The owners of this set vet all of the fonts they make available. So while I would lean towards unlikely, the reinstalled font may have indeed come from a damaged source, and Font Book is telling you so. Uninstalling your test font removed that copy of the font. When you add fonts to Font Book in the default manner, it copies all fonts you add to the Fonts folder within your user account. The same font can't suddenly go from okay to mangled. How is it possible? The only reasonable answer to me is Font Book isn't working properly.Īgreed. In the above case, the "fault" was nothing more than the permissions had changed on all of the fonts by moving them out of an OS controlled folder.

That doesn't make them bad, just old methods that are still completely harmless and still completely usable. Some are deprecated (old methods that aren't supposed to be used anymore). What Font Book marks with caution symbols can be just about anything. That's how useless Font Book's validation routine is. It reported every "moved" font with a caution symbol. I added them back into Font Book as a new set and ran validation again. The fonts themselves weren't rewritten in any way, so it was literally impossible for them to be damaged in any manner. Being on the same drive, a move did nothing more than change all of the file table entries to note the new location of the fonts. I then moved all of the fonts in the /Library/Fonts/ folder to a new folder. Font Book of course said every font was clean. Anything marked with a yellow caution symbol means nothing.Īs a test, I once installed OS X from scratch on an erased drive.

Only if a font is marked in red (serious issues) should you avoid installing it. Font Book's validation routine is almost entirely useless.