Plan library-scale bug fixing project about fonts HOT 4 OPEN

We already have this. Repos based on the googlefonts-project-template will have a sources/config.yaml which identifies the sources to build. Running gftools-builder sources/config.yaml on any compliant repo should build the relevant sources. This is how gfautobuilder (which I mentioned in your issue) works. builder2 is merged now. I'm seriously considering making a switch which makes the actual build-the-font operations use fontc instead of fontmake.

from fonts.

This is something I have been thinking about. There is a speadsheet here which tracks the library-wide fails and gives suggestions for how to fix them. Many of the issues can be scripted or hotfixed, but the best way to start is to track down as many upstream repos as we can, which I have been working on.

from fonts.

Adobe Fonts have also been working on this per the adobe-fonts fontbakery profile, made a Google Sheet to triage with me, and then drove a fonttools hotfix process using internal scripting with results posted to Drive only.

They identified the following indic fonts that lack a Rupee character, so adding that will be a good priority small-fix commission :)

• Kavivanar
• Modak
• Palanquin
• Palanquin Dark
• Pavanam
• Sumana

from fonts.

It would be helpful to fontc testing and adoption if we could include the ability to find the sources and identify which specific ones to compile as part of this. This enables us to test build things (googlefonts/fontc#724).

from fonts.