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 Sofia Sans #3799

Closed
RosaWagner opened this issue Sep 3, 2021 · 3 comments · Fixed by #5654, #5655, #5656 or #5657
Closed

Add Sofia Sans #3799

RosaWagner opened this issue Sep 3, 2021 · 3 comments · Fixed by #5654, #5655, #5656 or #5657
Assignees
Labels
I New Font II Commissioned Commissioned project to do
Milestone

Comments

@RosaWagner
Copy link
Contributor

RosaWagner commented Sep 3, 2021

Unblock PR #2889
upstream: https://github.com/lettersoup/Sofia-Sans

Problem of non-orthogonal design space.

  • We can either convince the author to repair his designspace
  • Or we only onboard static TTF and forget about the VF
  • onboard it under another name
@RosaWagner RosaWagner added -- Needs Upstream Resolution Upstream fix required before moving forward I New Font labels Sep 3, 2021
@RosaWagner RosaWagner added this to the 2021 Q4 milestone Sep 3, 2021
@RosaWagner RosaWagner modified the milestones: 2021 Q4, 2022 Q1 Sep 9, 2021
@RosaWagner RosaWagner added the II Commissioned Commissioned project to do label Oct 15, 2021
@vv-monsalve
Copy link
Collaborator

vv-monsalve commented Mar 31, 2022

After last work was done to have a working VF, these were the considered options:

  • Publishing it as a static font.
    Would support the current fonts in use in Sofia. But not having VF option until Avar 2 table is available
    • Decision: No, with so many styles, this misses the "compress" benefit; and avar2 is still in a very early phase.
  • Publishing it as a VF.
    As a different font, with another name or suffix e.g. Sofia Sans Libre. as it would not give support current fonts
    • Decision: No, there's a huge amount of usage in docs/slides that are imported to Drive using the current family name, and document fidelity is important
  • Publishing four single wght axis. E.g. Sofia Sans ExtraCondensed.
    No need to suffix or different name; will have the VF benefits, would give support to current fonts in use, would be possible to update it to a single Sofia Sans vf once Avar 2 table is life
    • Decision: Yes, this can be compatible for document import in terms of avar space, and gets some of the "compress" benefits, and Width axes styles aren't available at all in Workspace at the moment, so this is necessary.

@davelab6
Copy link
Member

Thanks @vv-monsalve , I edited your comment to add explanations of the decisions.

@RosaWagner RosaWagner modified the milestones: 2022 Q1, 2022 Q2 Apr 1, 2022
@RosaWagner RosaWagner modified the milestones: 2022 Q2, 2022 Q3 Jul 1, 2022
@vv-monsalve vv-monsalve modified the milestones: 2022 Q3, 2022 Q4 Aug 11, 2022
@RosaWagner RosaWagner modified the milestones: 2022 Q3, 2022 Q4 Sep 15, 2022
@vv-monsalve vv-monsalve removed the -- Needs Upstream Resolution Upstream fix required before moving forward label Nov 18, 2022
@vv-monsalve
Copy link
Collaborator

vv-monsalve commented Nov 30, 2022

From the above decision, four PR will be made:

@vv-monsalve vv-monsalve linked a pull request Nov 30, 2022 that will close this issue
@RosaWagner RosaWagner moved this from Todo to Live in Google Fonts Mar 3, 2023
@RosaWagner RosaWagner moved this from Live to In dev in Google Fonts Mar 9, 2023
@RosaWagner RosaWagner moved this from In Dev / PR Merged to Live in Google Fonts Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment