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 Homecomputer VF fonts #3425

Closed
2 of 7 tasks
davelab6 opened this issue May 14, 2021 · 19 comments · Fixed by #6919, #6917, #7025 or #7026
Closed
2 of 7 tasks

Add Homecomputer VF fonts #3425

davelab6 opened this issue May 14, 2021 · 19 comments · Fixed by #6919, #6917, #7025 or #7026
Assignees
Labels
I New Font II Accepted Non-commissioned projects that are accepted for onboarding II Custom axes Contains unregistered MS axis (even if registered by GF)
Milestone

Comments

@davelab6
Copy link
Member

davelab6 commented May 14, 2021

https://github.com/jenskutilek/homecomputer-fonts

Related to #254 by the same designer

Production notes:

  • Robot QA
  • Open issues about (stat, winAscent, license, repo structure, clean up)
  • Designer has fixed the issues
  • New robot QA
  • Visual QA
  • Package fonts
  • Prepare tweet
@jenskutilek
Copy link

I've added separate issues for the custom axes: #3697 (BLED), #3699 (SCAN)

@RosaWagner
Copy link
Contributor

@jenskutilek Do want us to have a call so we update each other on the process?

@jenskutilek
Copy link

I spent three hours last night trying to "dumb down" the fonts so they fit Google Fonts requirements, but for every reported problem I solve, I keep hitting a new roadblock. I'm slowly getting the feeling that it just isn't worth putting more work into this.

  • I had to convert the outlines to cubic even though the original source was drawn with quadratic curves, because otherwise fontmake won't build the static fonts
  • I invented new style names for the Bleed and Scan axes, only to have fontbakery complain that they don't fit the WWS requirements (width and weight names really don't apply here)
  • Lots more errors and warnings, most of them for things I had a good reason to do this way (vertical metrics, gasp table).

Everything was fine as it was, now I have two repos with lots of duplicated code and still nothing works…

@RosaWagner
Copy link
Contributor

@jenskutilek you don't have to go through this alone. Again, I am happy to have a call to explain the reasons of some requirements, how GF works and which process we apply in which case…

@RosaWagner RosaWagner removed a link to a pull request Oct 20, 2021
@RosaWagner RosaWagner added -- Upstream is working on it Designer is making changes in the upstream repo and removed - In Progress labels Oct 29, 2021
@RosaWagner RosaWagner modified the milestones: 2021 Q4, 2022 Q1 Dec 2, 2021
@RosaWagner RosaWagner removed this from the 2022 Q1 milestone Mar 11, 2022
@vv-monsalve vv-monsalve added II Submission pending proposal for non-commissioned fonts suggested in the issue tracker and removed -- Needs confirmation from upstream or onboarder labels Sep 5, 2023
@vv-monsalve
Copy link
Collaborator

Considering its historical concept, it was decided to onboard it with Latin Kernel only + Vertical Metrics exception

@vv-monsalve vv-monsalve moved this from In Progress to PR Upstream in Google Fonts Sep 5, 2023
@vv-monsalve vv-monsalve removed the -- Needs Upstream Resolution Upstream fix required before moving forward label Sep 7, 2023
@RosaWagner RosaWagner added II Accepted Non-commissioned projects that are accepted for onboarding and removed II Submission pending proposal for non-commissioned fonts suggested in the issue tracker labels Sep 12, 2023
@vv-monsalve vv-monsalve moved this from PR Upstream to In Progress in Google Fonts Sep 19, 2023
@chrissimpkins chrissimpkins modified the milestones: 2023 Q3, 2023 Q4 Oct 2, 2023
@vv-monsalve
Copy link
Collaborator

The above issues have been discussed and solved. A new one has emerged:

@vv-monsalve vv-monsalve moved this from In Progress to PR Upstream in Google Fonts Oct 26, 2023
@github-project-automation github-project-automation bot moved this from PR Upstream to In Dev / PR Merged in Google Fonts Nov 15, 2023
@simoncozens
Copy link
Collaborator

I added another variant font but failed to tell anyone. Carrying on at #6980.

@vv-monsalve vv-monsalve mentioned this issue Nov 21, 2023
8 tasks
@vv-monsalve
Copy link
Collaborator

vv-monsalve commented Nov 21, 2023

Hi @simoncozens, I'm aware of the new color font. As said in one of the meetings, we'll onboard the families referenced in this issue first, the "main" B/W fonts, as the colored version was only included recently, and check the main version's performance before adding this one.

The colored will still need the QA and font production job in preparation for a PR, including registering the new custom Axis + changing the "Color" bit in the name. I've assigned it to myself and marked it as Q1-2024.

cc @jenskutilek

@vv-monsalve vv-monsalve reopened this Nov 24, 2023
@github-project-automation github-project-automation bot moved this from In Dev / PR Merged to Todo in Google Fonts Nov 24, 2023
@vv-monsalve vv-monsalve moved this from Todo to PR Upstream in Google Fonts Nov 24, 2023
This was linked to pull requests Nov 28, 2023
@github-project-automation github-project-automation bot moved this from PR Upstream to In Dev / PR Merged in Google Fonts Nov 29, 2023
@vv-monsalve vv-monsalve removed the -- Requires Axis Registration Variable axes are not yet registered label Feb 27, 2024
@vv-monsalve vv-monsalve moved this from In Dev / PR Merged to Live in Google Fonts May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I New Font II Accepted Non-commissioned projects that are accepted for onboarding II Custom axes Contains unregistered MS axis (even if registered by GF)
Projects
Status: Live
7 participants