Quote:
Originally Posted by bethrosengard  You should know by now if you've read the above: It controls the font optimization process; it allows WYSIWYG for fonts; it warns you when fonts are corrupt (and probably more that I'm not aware of).> |
good riddance. I am not getting these corrupt font errors, but I might delete FontCacheTool just to get rid of the optimization. I can't tell you how many times I have been forced to stare at the "optimizing font menu" screen while loading a Word doc.
How does FontBook do it? seems to work far smoother than Office. Is it an API that other apps can use? If so, MS really should be using that rather than creating a slow, unstable version.