To this end, it really helps to have a decent font management application on hand. If you want to use any other fonts, enable them only when you want to use them, and disable them the rest of the time. Confine your installed fonts to just the fonts that come with a clean installation of Mac OS X, and no more. A document that requires more fonts than that would be pretty rare.Ī sound, basic approach to fonts is to keep your font list lean and mean. After all, how many fonts do you actually use, intentionally, at one time? Probably one or two at most maybe, if you're writing a book, five at the outside. There's no point adding a lot more to the list of installed fonts. These are already making your font lists too long to manage easily, and giving applications too much work to do in dealing with them. You've got too many fonts already, by default (the fonts that are present in any clean installation of Mac OS X, in /System/Library/Fonts and /Library/Fonts). Now, in general, we can certainly recommend that you should never install a whole bunch of fonts. We wrote back suggesting a font problem as the source of the crash to Tracey, who confirmed that in fact a whole bunch of fonts had been installed just before the crashes started. The entries containing the words "FontMenu" suggest that Word is having trouble forming its Font menu, something it obviously must do as it starts up. Notice the pervasive presence of the term "Font" in that list of activities. # 9 0x9299ece0 in _Z23_CreateStandardFontMenuP8MenuDatatsmPm 0x00000054 # 7 0x92a7bc2c in _Z20BuildFontNamesRecordmsm 0x00000068 (HIToolbox
0 Comments
Leave a Reply. |