search

googlefonts / fontc

Where in we pursue oxidizing (context: https://github.com/googlefonts/oxidize) fontmake.
Apache License 2.0
76 stars 13 forks source link

External GlyphData.xml files #766

Open simoncozens opened 6 months ago

simoncozens commented 6 months ago

Some fonts in the GF catalogue expect to use external GlyphData.xml files to determine categories and production names for glyphs with well-known names. Is this in scope for fontc? (Alternately, we can require that babelfont preprocesses such Glyphs files to bake the data into the sources.)

cmyr commented 5 months ago

I think we could reasonably handle this, although it does complicate a few of our assumptions (specifically that we can use some tricks at compile time to bake in the contents of GlyphData in such a way as to make it very efficient to access) but we could definitely add a slow path for when additional overrides are specified at runtime.

rsheeter commented 5 months ago

Which specific fonts use this and what would the impact of not having it be?

simoncozens commented 5 months ago

I know at least the Noto Arabic fonts use it. I can't tell which other fonts use it. Not having it means glyph categories are wrong and shaping breaks.