googlefonts / googlefonts/axisregistry

Add "auto" to axes that interact with other axes

Open
#72 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
43
Forks
17
PR merge metrics
No merged PRs in 30d

Description

In discussing the axis registration protocol with @vv-monsalve today, we compared the Cursive and Wonky axes

- https://fonts.google.com/knowledge/glossary/wonky_axis
- https://github.com/googlefonts/axisregistry/blob/main/Lib/axisregistry/data/wonky.textproto
- https://fonts.google.com/knowledge/glossary/cursive_axis
- https://github.com/googlefonts/axisregistry/blob/main/Lib/axisregistry/data/cursive.textproto

@thundernixon invented this nice 'auto' `0.5` value in the Cursive axis of Recursive, which controls the cursive glyph substition along the Slant axis, allows users to get cursive forms at the max slant, or turn them on manually sooner, even with slant 0 (min), or, keep them off at slant max.

@sponcey and @flaviazim and @arialcrime set up the Wonky axis in Fraunces in a similar way, where the Optical Size axis will show Wonky glyphs at large sizes (22+) and normal glyphs at smaller sizes, and the Wonky axis can manually obtain NonWonky glyphs at large sizes:

Screen Shot 2022-08-26 at 2 10 02 PM

However this doesn't work for small sizes to turn Wonky on; arguably this is correct as Wonky isn't useful at small sizes and interferes in readability:

Screen Shot 2022-08-26 at 2 04 51 PM

So, we wonder about updating the axis definition and the Fraunces project be updated to support an Auto value, next time the project advances to fix all other known bugs. This will be useful to inform the next project that uses the Wonky axis, whatever that is :)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.