- #Fontbook fix mac word 2016 crashing yosemite update#
- #Fontbook fix mac word 2016 crashing yosemite professional#
Not that Font Book's warnings are usually worth a hill of beans. Since Font Book flagged it as having a serious error, it was likely damaged at some point. Those still work, so that itself wouldn't have been the problem. So, both disappeared when that would never normally happen.įrom 15 years ago, that would likely have been a Type 1 PostScript font. The cache file was removed, but was also incorrectly cross-linked to a font. I'd be concerned there is file corruption across the entire drive.
#Fontbook fix mac word 2016 crashing yosemite update#
The only exception is an OS upgrade or update where each has to give itself permission to remove, add, or alter files. And the OS itself won't let any app, not even one of its own, do such a thing in the System folder. I don't know what happened there, but the command given above won't delete fonts. I had to re-download all the fonts (oddly, they were system fonts that were deleted). The fonts were entirely gone off my computer-didn't show up in the font folders at all, and were grayed out in FontBook. The rest all recognize fonts you open and close on the fly.
#Fontbook fix mac word 2016 crashing yosemite professional#
It's the only professional app I've seen with this behavior. You'd think MS would have fixed this by now. Not that this may help, but it's a simple place to start.Īlso, and I mention this because a lot of folks don't know it, any fonts you activate after Word is already running will not show up in the app. Launch any Office 2011 app and it will build a new font cache file. With all Office 2011 apps closed, put the file Office Font Cache from the above location in the trash. The tilde ~ means your user account, not the root Library folder.
~/Library/Application Support/Microsoft/Office/Preferences/Office 2011/Office Font Cache Which version of Office are you using? If it's Office 2016, the apps no longer maintain their own font cache. Since it was working before, we can presume there's nothing wrong with the font. … It is suddenly, after the last update, not available. I'm having issues with a third-party OTF font not showing up in Word, too. Which means they were never missing since Font Book can't reinstall anything. The command only removes cache data, not fonts.įortunately FontBook makes it easy to reinstall. I tried that Terminal trick… and it deleted several fonts including Times New Roman. This will clear Font Book's database and the cache files of the user account you logged into in Safe Mode. Let the Mac finish booting to the desktop and then restart normally. 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). So hold the Shift key until you get to the desktop. It just takes longer to get to the desktop in Safe Mode. Whether it's a Safe Mode boot or a normal one, you get the same progress bar. You can let go of the Shift key at that point. Keep holding the Shift key until you see a progress bar towards the bottom of the screen. Restart your Mac and immediately hold down the Shift key when you hear the startup chime to boot into Safe Mode. Or at least, 99% of the time, that's what's wrong when the fonts are listed in Font Book, but none, or only some of them appear in your apps. What's wrong is Font Book's database is corrupt. All of your fonts are still on the drive.
FontNuke doesn't delete fonts, it deletes font cache data.
0 kommentar(er)
