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

'YOPQ' fvar default does not match registered fallback name #319

Open
tphinney opened this issue Jan 4, 2024 · 0 comments
Open

'YOPQ' fvar default does not match registered fallback name #319

tphinney opened this issue Jan 4, 2024 · 0 comments
Assignees

Comments

@tphinney
Copy link
Collaborator

tphinney commented Jan 4, 2024

Fontbakery error report

Validate defaults on fvar table match registered fallback names in GFAxisRegistry.
Check ID: com.google.fonts/check/gf_axisregistry/fvar_axis_defaults
Check that axis defaults have a corresponding fallback name registered at the Google Fonts Axis Registry, available at https://github.com/google/fonts/tree/main/axisregistry

This is necessary for the following reasons:

To get ZIP files downloads on Google Fonts to be accurate — otherwise the chosen default font is not generated. The Newsreader family, for instance, has a default value on the 'opsz' axis of 16pt. If 16pt was not a registered fallback position, then the ZIP file would instead include another position as default (such as 14pt).

For the Variable fonts to display the correct location on the specimen page.

For VF with no weight axis to be displayed at all. For instance, Ballet, which has no weight axis, was not appearing in sandbox because default position on 'opsz' axis was 16pt, and it was not yet a registered fallback positon.

🔥 ScienceGothic[YOPQ,slnt,wdth,wght].ttf
🔥 FAIL
The defaul value YOPQ:122.0 is not registered as an axis fallback name on the Google Axis Registry. You should consider suggesting the addition of this value to the registry or adopted one of the existing fallback names for this axis: [name: "Normal" value: 116.0 ] [code: not-registered]

Commentary

Clearly the notion of Axis Registry defaults plus their usage is at odds with how this axis was defined. The “Normal” value of 116 is font-specific as it represents a per-mill-of-em amount. So if two different families ever have the same value default/normal value, that is pretty much a coincidence. Most likely one could have ten or twenty families and never repeat the same default, just because of how the axis was defined.

I can easily imagine ways to make the axis scale font-independent with a “normal” that will be zero or 100 for all fonts. But that is not what is in the Axis Registry today.

I have no idea what I should actually do in the font, or what should get added to the Registry if two (or more) fonts disagree about what constitutes “Normal”

@tphinney tphinney self-assigned this Jan 4, 2024
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