FontLab Forum
2012-05-22, 07:42:35 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: BUG: fonts not listed on font menu in Word for Mac 2008  (Read 1788 times)
siggy
Hero Member
*****

Karma: +0/-0
United States United States

Posts: 28


« on: 2010-09-22, 12:57:57 »

I'm having problems with PostScript OpenType fonts made from FOG 5 not showing up in the font menu for Word for Mac 2008. This is not a problem if you generate the same font as a TrueType OpenType font. Also, Adobe PostScript OpenType fonts don't have this problem.

If Adobe PS/OT fonts can show on the font menu, then why not PS/OT fonts made from Fontographer 5? I've tried using both the auto name building tools and simply filling out the names manually.

Someone at Microsoft looked at the font files I made, also comparing them to an Adobe font file, and found that a "name table" field is blank in the PS/OT font made in FOG 5, but not blank if made as a TT/OT font, and also not blank in the Adobe PS/OT font.

The blank field in my PS/OT is the one that should list the "Regular" style of the font. Is there a reason this field is left blank when the PS/OT font is generated in FOG 5?

Thanks!
__________________________________________________
SOLUTION >>>


I stumbled onto a work-around. I generated a bunch of PS/OT fonts, and then found that some of them were listed on the font menu, but other weren't. I checked the Fontographer files, and found that the fonts that showed on the menu had one name field left completely blank; the fonts that didn't show on the font menu, had that same field filled in. Totally backwards!

In the Font Information dialog box in Advanced mode, in the Names section, the 2nd line is called  "Typographic style name." This can be auto-filled by checking the Auto box at right, or it can be manually edited by un-checking the box.

Most of the fonts I generated had this line auto-filled as "Regular." These fonts did not show on the font menu in Word for Mac 2008. However, this same field was left blank on a few fonts, and those fonts showed up on the font menu with no problem.

The work-around? Leave this field blank! I generated both TT/OT and PS/OT fonts with this field blank, and they show on the font menu just fine.

Hey FontLab -- can you check into why this field causes problems in PS/OT fonts when it's filled in Fontographer, yet ends up blank in the name table of the generated font? Again, it's not a problem for TT/OT fonts. Many thanks!


« Last Edit: 2010-09-22, 19:23:00 by siggy » Logged
Arno Enslin
Hero Member
*****

Karma: +8/-0
Germany Germany

Posts: 98



« Reply #1 on: 2010-09-23, 13:24:44 »

There is one slight difference only with regard to the name table of TrueType and PostScript flavored OpenType fonts. From the OT spec (http://www.microsoft.com/typography/otspec/name.htm):

Full font name; this should be a combination of strings 1 and 2. Exception: if the font is “Regular” as indicated in string 2, then use only the family name contained in string 1.
An exception to the above definition of Full font name is for Windows platform strings for CFF OpenType fonts: in this case, the Full font name string must be identical to the PostScript FontName in the CFF Name INDEX.


Except from that the name tables should be identical.

But if you want to make out those differences in future, don’t ask Microsoft, but decompile the name table of the TT-OT and the PS-OT version of your font with the help of TTX and compare the tables: http://sourceforge.net/projects/fonttools/
Logged
siggy
Hero Member
*****

Karma: +0/-0
United States United States

Posts: 28


« Reply #2 on: 2010-09-24, 16:45:36 »

Thanks, but I have a working relationship with Microsoft; I can consult with them if I want to. They were very helpful in diagnosing the problem as a name table issue -- which I wouldn't have figured out without them. I wouldn't even have known to look for it.
Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!