Office Fonts Not Installed with Office 365 (2016) on Mac OS Sierra

Question

I just installed Office 365 Home on Mac OS Sierra. It's working (I can open Word, for instance, create/view files, print, etc.) but I noticed the Office fonts (Calibri, Constantia, Cambria, etc.) were not installed. I could extract them all from another computer with those fonts and install them manually, but would prefer to find out why they weren't installed, since something else that I may not even be aware of may also have gone wrong during the installation.

Answer 1

Right click on any Office app > Show Package Contents > Contents > Resources > and you should find various font folders in each app.

Answer 2

These instructions are accurate, but to install the fonts in Font Book, I had to drag them out of the Contents->Resources folder and toss them on the desktop. I had Word also running at the time and that may have also been why I couldn't install the fonts directly from the folder path suggested by adydog.

Answer 3

This page has the best explanation of Office and fonts that I know of:

http://www.jklstudios.com/misc/osxfonts.html

Answer 4

Unlike 2011, 2016 is written in the very latest ( I hope ) Apple code, Which uses Sandboxing. A method where various components of an application are placed in "Container Directories".

Okay here is where the "Roll your eyes and wonder, thoughts" come to mind. ,

Each Application rather than reading fonts from one location and creating a Cache file for the application, each application has a complete set of fonts placed in each of the containers for each application so instead of 100 fonts on your computer you now have:

100 for the entire computer

100 for Word 2016

100 for Excel 2016

100 for PowerPoint 2016

100 for OutLook 2016

100 for OneNote 2016 

So If your Fonts took up 20 MB of space on Your Hard drive before install Office 2016 You have 600 fonts that use 120 Mb of Space (note: I am pulling numbers out of the air for illustration only)  While if you have an SSD (Solid State Hard Drive) everything is available almost instantly, on a Standard Hard Drive it has run to load those 600 Fonts. And, for some reason, Font book doesn't recognize those fonts. So you may have some font issues and don't know about it. Why Microsoft could have put one set of fronts in the Group Container folder and had each application refer to that master location, I will never know. So they are wasting valuable space that doesn't need to be. Sometimes, common sense logic just doesn't dawn on them.

Anyway, this explains, while you appear to have fonts, but can not see them in Fontbook.

With the cost of SSD and computers in general, It will be many many years before SSD will replace Standard Hard Drives. And the questionable reliability of SSD, it will a long time before slow loading will disappear. 

_________

Disclaimer:

The questions, discussions, opinions, replies & answers I create, are solely mine and mine alone and do not reflect upon my position as a Community Moderator.

Answer 5

OK, so what this means is, I have to install them manually from another computer that has them. Which I will do.

FWIW I've worked in IT for many years. I can follow what you're telling me. But the bottom line of it all is pretty freaking stupid. Time for MS and Apple to go back to the drawing board and devise a more rational scheme for developing and running applications.

Having fonts installed on a systemwide level was intended to provide users with a common base of typefaces they could use, in everything. It also reflected the original reality of typefaces ... before the advent of graphical fonts ... which is that they were stored in printers, therefore, any program that printed called on the same fonts. And later, things like network font managers were devised for printing/publishing shops, so multiple computers could call upon the same font repository.

It was a smart idea, if you ask me (and no, you didn't, but I'm saying it anyway). That Apple and MS would, together, break that scheme into something incredibly unintuitive, is (in two words) monumentally stupid.

If little old me ... non-developer that I am ... can recognize how dumb this is, no one at Apple or MS has anything resembling a valid excuse for not knowing it.

Anyway, thanks for letting me know why I have a lot of unnecessary work to do.