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

Use custom VF axes for CRT bleed and scanlines #2

Closed
felipesanches opened this issue May 14, 2021 · 3 comments
Closed

Use custom VF axes for CRT bleed and scanlines #2

felipesanches opened this issue May 14, 2021 · 3 comments

Comments

@felipesanches
Copy link

it is very cool that you've got variation axes for CRT bleed and scanlines. I just disagree to the use of wdth and wght for those variations

@jenskutilek
Copy link
Owner

I agree. Any reservations against using custom axes regarding the prospective release on Google Fonts, @davelab6?

@RosaWagner
Copy link

RosaWagner commented Jul 15, 2021

The problem with the custom axes is that they need to be registered, and the process is quite long and the font can be pending for weeks/month. I would advise to build a case in this issue: google/fonts#3425 with images so all (like in: google/fonts#2849)

@jenskutilek
Copy link
Owner

First I thought you meant the axes need to go through the OpenType specification axis registration process and was prepared to give up ;) But now I see Google has its own registry.

I changed the axis names in the fonts and added proposals for the new axes to be included in the Google Fonts Axis Registry: google/fonts#3697, google/fonts#3699

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants