Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Specify and implement a "StyleName recommendation" check

See original GitHub issue

$ ./fontbakery-check-ttf.py -s ../mada/Mada-Black.ttf 
…
ERROR    Mada-Black.ttf: Warning: Windows-only Opentype-specific StyleName should be set to "Regular".

I have no idea what is “Windows-only Opentype-specific StyleName” or what to do with this error.

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:18 (13 by maintainers)

Top GitHub Comments

1reaction

khaledhosnycommented, Jul 30, 2016

Windows old font APIs allow only four fonts per family, so for any given family there can only be the following four fonts:

Family (id=1)	Subfamily (id=2)	Full name (id=4)
Foo	Regular	Foo Regular
Foo	Bold	Foo Bold
Foo	Italic	Foo Italic
Foo	Bold Italic	Foo Bold Italic

To support families was more than four fonts, typographic family name and typographic subfamily name have been introduced, and the extra fonts have to be structured like this:

Family (id=1)	Subfamily (id=2)	Full name (id=4)	Typograpghic Family (id=16)	Typographic Subfamily (id=17)
Foo Light	Regular	Foo Light	Foo	Light
Foo Medium	Regular	Foo Medium	Foo	Medium
Foo Black	Regular	Foo Black	Foo	Black

So for the old APIs these are seen as separate families with just the regular style each, ad for newer APIs that support the typographic name they all belong to the Foo family. For the first four styles name ids 16 and 17 can be missing or identical to 2 and 4, respectively.

0reactions

alexeivacommented, Aug 1, 2016

DemiBold and Book were legacy names, which are served on GF as SemiBold and Regular.