![]() But we're dealing with dozens new font files added to our working pool of hundreds of font files every year. (For example, one font didn't set up their unicode in a way that Office programs liked, so Publisher couldn't access swashes and ligatures.) The result is we try both, go with the one that works best, and move on. We've tracked that issue to how the foundery programs each font. The reason we don't have an office-wide policy of "install this font type only"? Because we use a lot of MS Office programs and they sometimes have trouble with a font-it's usually the OTF, although sometimes it's the TTF. ![]() ![]() ![]() (There are other problems with Publisher, but this isn't a the place for that rant.) Microsoft Publisher has no trouble switching between TTF and OTF if they have the same name. (We've had a lot of trouble with Humanist521 doing this, for example.) Without a constant audit of every font file on every computer in the company, there's no way to manage it. Well, some computers have the TTF installed, some have the OTF installed, and some fonts only come in TTF but get register as/converted to OTF but only on some fomputers for some unknown reason.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |