Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Axis default vs font naming #3362

Open
aaronbell opened this issue Jun 29, 2021 · 0 comments
Open

Axis default vs font naming #3362

aaronbell opened this issue Jun 29, 2021 · 0 comments

Comments

@aaronbell
Copy link
Contributor

In converting the Fraunces font to the United Font Repro and updating the build process, I encountered an issue wherein the font name table lists the font name as Fraunces 9pt SuperSoft Black when installed as the font only contains Thin and Black masters, with the Black master set as default in the designspace.

While this doesn't have a significant impact on the performance of the font, as the elible font naming has been correctly set, it does cause some confusion for users who are expecting that they're installing a variable font, not a static instance. See:
undercasetype/Fraunces#250
undercasetype/Fraunces#209

It is relatively straightforward to change the name table to adjust the way that the font is named / weighted, but that throws two errors due to the default location on the axis being 900:

  • 🔥 FAIL TYPOGRAPHIC_SUBFAMILY_NAME for Win "Italic" is incorrect. It must be "Black Italic". [code: bad-typo-win]
  • 🔥 FAIL OS/2 usWeightClass is '400' when it should be '900'. [code: bad-value]

AFAIK, the only case for not changing the name table settings (aside from the fail above) is that if variable font technology doesn't work, whatever is listed as default will be shown. So someone seeing "Fraunces" and getting a Black-weight font might be confusing as well, but I believe this scenario to be less and less likely as variable font tech becomes widely available. As such, I am leaning towards changing the font name (and usWeightClass) to follow user expectations of Regular.

IMO, I think that in the case of a Variable font, the above two FAILs might be better set as WARN.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant