Style problem in Microsoft Office about glow-sans HOT 3 CLOSED

Thank you for the quick response. You might also need to change the OS/2.fsSelection too to reflect the weight change according to name specification from Microsoft.

Also from the site,

While some platforms or applications do not have this constraint, many existing applications that use this pair of names assume that a Font Family name is shared by at most four fonts that form a font style-linking group, and that Font Subfamily names would reflect one of the four basic styles, regular, italic (or oblique), bold, and bold italic (or bold oblique). To be compatible with the broadest range of platforms and applications, it is strongly recommended that fonts should limit use of Font Family in this manner.

Thus, it might be more reasonable to let both platforms use the same set of constrain, unless Mac softwares are able to differentiate family name other than Regular and Bold.

from glow-sans.

A quick run and check, I think i have found the code for the name table to be fixed:

    record(familyName,        `Glow Sans ${langStr} ${widthStr}`),
    record(subfamilyName,     weightStr),

I think you may want to update the code to be:

if (weightStr == "Regular" || weightStr == "Bold"){
    record(familyName,        `Glow Sans ${langStr} ${widthStr}`),
    record(subfamilyName,     weightStr),
} else {
    record(familyName,        `Glow Sans ${langStr} ${widthStr} ${weightStr}`),
    record(subfamilyName,     `Regular`),
}

The same fix would need to be fix across languages so maybe(?) put this code at the top for all languages:

if (weightStr == "Bold"){
    weightName1Str = "";
    weightName2Str = "Bold";
} else if (weightStr == "Regular"){
    weightName1Str = "";
    weightName2Str = "Regular";
} else {
    weightName1Str = weightStr;
    weightName2Str = "Regular";
}
...
    record(familyName,        `Glow Sans ${langStr} ${widthStr} ${weightName1Str}`),
    record(subfamilyName,     weightName2Str),

from glow-sans.

Thank you for pointing out the problem and working on further research. I think I've realized what is going wrong. The latest version follows the naming scheme for Macintosh (platformID=1) but actually has platformID=3 (Windows), causing unexpected behaviors on both platforms. We will differentiate the name records for different flatforms in the next version.

The working name table records for nameID = 1, 2, 4 might be,

[{
    "platformID": 1,
    "encodingID": 1,
    "languageID": 1033,
    "nameID": 1,
    "nameString": "Glow Sans SC Compressed"
},
{
    "platformID": 1,
    "encodingID": 1,
    "languageID": 1033,
    "nameID": 2,
    "nameString": "Book"
},
{
    "platformID": 1,
    "encodingID": 1,
    "languageID": 1033,
    "nameID": 4,
    "nameString": "Glow Sans SC Compressed Book"
},
{
    "platformID": 3,
    "encodingID": 1,
    "languageID": 1033,
    "nameID": 1,
    "nameString": "Glow Sans SC Compressed Book"
},
{
    "platformID": 3,
    "encodingID": 1,
    "languageID": 1033,
    "nameID": 2,
    "nameString": "Regular"
},
{
    "platformID": 3,
    "encodingID": 1,
    "languageID": 1033,
    "nameID": 4,
    "nameString": "Glow Sans SC Compressed Book"
}]

from glow-sans.