-
Notifications
You must be signed in to change notification settings - Fork 42
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
Bungee (including Layers fonts) no longer sorts into desktop-friendly menus #120
Comments
I notice the released fonts do not contain name IDs 16 and 17. Setting those to the desired values likely fixes this problem. |
Do you consider Tint and Spice to be part of the "Bungee" family, or should they be grouped as their own? The former makes most sense as the color fonts don't have a common family name distinct from the basic group. How about this "preferred family + style name" grouping:
(Taking into account the fixing of names the Layered Rotated fonts, as noted in #119) |
If this works for you, it works for me! I think it will be good to make this consistent with v1 unless there is a reason to change it.
I hear that, though maybe since Bungee Spice was released as a separate family, there is precedent to let that and Tint remain their own families. So I guess I have a slight preference towards that but could go either way. |
That can work, too. Like this?
|
In desktop apps (including Adobe), Bungee’s styles no longer sort into nice families (Bungee, Bungee Layers, Bungee Rotated, etc.)
I figure this is an intentional change and comports with Google Fonts practice to only include weights and italics with the same family name? And I’m guessing a decision has been made that it’s okay that these new names will break compatibility with older documents?
I’m wondering if you think this separation also needs to apply to Layers fonts, which Google Fonts does not distribute, and where it is especially helpful to have the styles sorted into the same family for easy flipping between layers?
Sorry if these questions are annoying and/or being asked too far after-the-fact...pretty must just want to confirm that this stuff is intentional before letting it go.
The text was updated successfully, but these errors were encountered: