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

Add "auto" to axes that interact with other axes #72

Open
davelab6 opened this issue Aug 26, 2022 · 2 comments
Open

Add "auto" to axes that interact with other axes #72

davelab6 opened this issue Aug 26, 2022 · 2 comments

Comments

@davelab6
Copy link
Member

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

@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 :)

@RosaWagner
Copy link
Contributor

Would this also apply to VOLUME which is interacting with FLAIR?

@vv-monsalve
Copy link
Contributor

Cursive is a boolean (pseudo) axis that controls the substitution of glyphs to cursive forms, with that third "auto" position enabled. Wonky is currently a boolean axis that could be improved to include this same auto position.

Since Volume is a continuous range axis, and we are no longer including fallbacks per axis definition I don't see how it could be ruled per axis basis to be used in that way. Perhaps is something that could be enabled per font basis (STAT format 4. as I think Commissioner is already doing)

@davelab6?

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

3 participants