Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
FontBureau profile for checks on proposed new variation axes
See original GitHub issueI have just had a nice videocall with Mirko (@bghryct) in which he told me he’s interested in implementing FontBakery checks for the new variation axes proposed here: https://variationsguide.typenetwork.com/
I believe that we can use the same strategy that we’re using for the gf-axis-registry checks by employing textproto files for those axes. But I would place these new axes on a separate profile (Mirko suggested to call it the fontbureau profile). If these axes are added to the GFAxisRegistry in the future, it would then be super easy to migrate the textproto files into the googlefonts profile.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
you can send a PR adding them to this directory:
Lib/fontbakery/data/. There are already some other textprotos in there.@bghryct, please post here the contents of a textproto file for at least one of the newly proposed axes. The structure of such textproto files can be seen here: https://github.com/google/fonts/tree/fa38f09d14b5c976a5b0c140cdfbc562023fc38e/axisregistry