This means parsing the overrides in the source file, and then falling
back to the glyphdata when needed.
This also implements additional logic (ported from glyphsLib) for
determining the category for glyph names that might be alternates or
ligatures.
This is doing most of what fontools, is, with two notable exceptions:
fonttools does lookup based on production names, and also spends a bunch of time computing production names. I'm not sure if this is important for our purposes? (deferred to https://github.com/googlefonts/fontc/issues/780)
~fonttools has a fallback branch in the code that computes categories when they aren't found, and this fallback branch queries the Adobe Glyph List. We currently bundle the shorter version of this in layout-normalizer, and so maybe it's worth just putting this in fontdrasil?~ this is implemented
This means parsing the overrides in the source file, and then falling back to the glyphdata when needed.
This also implements additional logic (ported from glyphsLib) for determining the category for glyph names that might be alternates or ligatures.
This is doing most of what fontools, is, with two notable exceptions: