v2.3.0.post1
The MarkFeatureWriter was modified in #276 as follows:
-
If a
table GDEF { GlyphClassDef ... ; } GDEF;
is present in the features.fea, then the MarkFeatureWriter will use those groups to define what is a base glyph, ligature or mark glyph. When no GDEF GlyphClassDef definition is present, the current behavior doesn't change (fixes #261). -
When a mark glyph contains multiple
_
-prefixed anchors, we only assign that glyph to one markClass; we no longer associate it with multiple markClasses one for each_
-prefixed anchor that it may contain. Instead, we sort the glyph's anchor list by putting_bottom
and_top
anchors before all the rest, and then we only take the first anchor's name to define the glyph's markClass. This is the same heuristic used by Glyphs.app to resolve these ambiguous cases when generating the mark feature. It fixes a compilation error when the same mark glyph belongs to multiple mark classes that are used within the same mark lookup (notofonts/noto-source#122)
The version string in setup.py is now computed from git metadata using setuptools-scm.