-
Notifications
You must be signed in to change notification settings - Fork 20
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
Font naming and axes default #209
Comments
Consistent capitals for axes names sound good! For how to name the I agree that it isn't very intuitive, actually. Since there are 3 stops, some ideas:
@sponcey curious what ideas you may have :) |
I agree that's it rather cryptic, but at least it's somewhat functional. Part of the reason we kept the name short was because of the character limit for instance names. Additionally, there has been so much back and forth on this axis and figuring out the instance names, which really gummed up many aspects of the mastering for @arialcrime, as well as rolling it out to the mini site and the print specimen. @davelab6 If this is not essential to address for v1.0 release, can we flag this as something to take a look at for future releases? I'm hesitant to keep opening this issue back up because of the budget and time restraints. |
I'll need to check with the GF engineering team before it's final. I understand the process has been rough, but it's sadly still going to be rough. "s000" and "Soft" and "Hard" are the same length. |
I propose: Hard (0), Softer (50), Softest (100) |
This need to be fixed for v1.000, @vv-monsalve can do |
"Hard" doesn't feel descriptive to me of that area of the axis. The axis moves from Sharper to Softer, like a lens focusing. Or Crisp to Soft. |
That's fair. So propose: Sharper (0), Soft (50), Softer (100) |
https://github.com/google/fonts/blob/aa32de46068da0921045f2292e0373a679a542b1/axisregistry/softness.textproto#L9 also uses "Normal" at the moment, which is an option, although rather too normative and not descriptive enough for me. |
Before closing this issue, I'll need to arrange for updating the print specimen, web specimen, and this repo's README. |
How about Sharp (0), Softer (50), Softest (100)? |
@davelab6 Or: Sharp (0), Soft (50), Extra Soft (100)? |
Update fallbacks based on undercasetype/Fraunces#209 (comment)
https://github.com/google/fonts/pull/2677/files#diff-f3c2cbf017afa8f139a33c916d34cc02 is merged with Sharp (0), Soft (50), Extra Soft (100). |
@sponcey |
@davelab6 The instance names need to be updated too before this should be closed. |
Currently working to solve instance names taking these values. |
Please ping me if the site needs updating! |
The style name |
Dropping the current font in Wakamai Fondue shows some things that might not be intended:
The text was updated successfully, but these errors were encountered: