Upgrade Big Shoulders with opsz axis on Google Fonts

[yanone]

Hi,

I'm commissioned with updating Big Shoulders on Google Fonts.

I was wondering whether I shall clean up the repository structure to reflect the fact that the "Text" and "Display" families are no longer needed (for Google Fonts) or leave everything in place because they're still needed elsewhere.

Cheers

[xotypeco]

please feel free to clean it up. the city government has no opinion on Text and Display variants existing. they know that the two versions were a stopgap until the dual-axis version was available. I can make that transition work. the only other major lens into this repo besides Google Fonts is Adobe Fonts, and they, like the city government, can be managed on my end.

…

On Jan 15, 2025, at 9:37 AM, Yanone ***@***.***> wrote: Hi, I'm commissioned with updating Big Shoulders on Google Fonts. I was wondering whether I shall clean up the repository structure to reflect the fact that the "Text" and "Display" families are no longer needed (for Google Fonts) or leave everything in place because they're still needed elsewhere. Cheers — Reply to this email directly, view it on GitHub <#47>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMRMUXHP7Q43AX6WXBQEJVD2KZ6EXAVCNFSM6AAAAABVHRBEUKVHI2DSMVQWIX3LMV43ASLTON2WKOZSG44TAMJXG4ZTGNA>. You are receiving this because you are subscribed to this thread.

[yanone]

So, one of the changes is that "Text" and "Display" are not part of the opsz axis fallback names. This I need to change in order to onboard the complete VF to Google Fonts. I'm guessing that stuff wasn't defined yet back when Big Shoulders was initially onboarded. Instead, the allowed fallback names denote the intended sizes, so Big Shoulders 10pt and Big Shoulders 72pt are allowed.

Are they all using the the fonts in Workspace or via the webfonts API, rather than downloading statics (or VF) and installing them locally?

Because the API will continue serving the old fonts; they just won't be available for new users/documents under the old name. In that case I shall be completely free to rename them according to specs, but I wanted to hear your opinion first.

In case of Workspace it won't make a difference, because the font names will change in any case, whether "Text" & "Display" or "10pt" & "72pt". At the end, only "Big Shoulders" will be available, so new documents must use the new names in any case.

And the same should be true for Adobe in case of VF. It will be renamed in any case.

But in case the statics and/or VF need to remain available for download from the repo under the old names Text&Display, maybe I can extend the existing build script to allow generating both from the same source.

So I need to ask for your opinion on this once again before I start the work.

[xotypeco]

On Jan 23, 2025, at 7:45 AM, Yanone ***@***.***> wrote: So, one of the changes is that "Text" and "Display" are not part of the opsz axis fallback names. right, this is expectedThis I need to change in order to onboard the complete VF to Google Fonts. I'm guessing that stuff wasn't defined yet back when Big Shoulders was initially onboarded. Instead, the allowed fallback names denote the intended sizes, so Big Shoulders 10pt and Big Shoulders 72pt are allowed. correct! also expected. these names were part of the original plan.Are they all using the the fonts in Workspace or via the webfonts API, rather than downloading statics (or VF) and installing them locally?I’m fairly sure they’re downloading locally, not using Workspace or webfonts API, but I’m not positive. I’ll check with the city and get an answer for you.I do know the final answer will be that they aren’t worried about changing method of usage throughout the various departments; the head of the department dealing with this has been very clear that he’s OK with changing workflows to make sure everyone’s using final versions.my personal feeling is that the names Text and Display should go away entirely, because they’re misleading names for most people. Because the API will continue serving the old fonts; they just won't be available for new users/documents under the old name. In that case I shall be completely free to rename them according to specs, but I wanted to hear your opinion first. In case of Workspace it won't make a difference, because the font names will change in any case, whether "Text" & "Display" or "10pt" & "72pt". At the end, only "Big Shoulders" will be available, so new documents must use the new names in any case. this is fine.And the same should be true for Adobe in case of VF. It will be renamed in any case. But in case the statics and/or VF need to remain available for download from the repo under the old names Text&Display, maybe I can extend the existing build script to allow generating both from the same source. my hunch is that this is neither necessary nor desired, going forward, but I’ll check current processes from the city.So I need to ask for your opinion on this once again before I start the work.understood. I appreciate you pausing to do so. more very soon! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>