Open simoncozens opened 2 years ago
hm but then what's the point of marking a glyph as a Ligature in GDEF but then effectively treating it as a Base for mark feature, by attaching a mark-to-base rule?
Again, this would be fixed with the code in the GlyphsInfo3 branch.
How? This is a ufo2ft issue.
In Noto, I keep beating my head against https://github.com/googlefonts/glyphsLib/issues/756. Basically, the issue is this:
a-somescript
andb-somescript
and calls ita_b-somescript
.bottom
.I can get around it by setting all these glyphs manually to being bases (or alternatively by renaming all my anchors), but if I have a
bottom
anchor and some marks have a_bottom
anchor, that means I want them to attach together. I think it should be fine to match these anchors and issue mark-to-base rules for these glyphs if no_1
etc anchors are present (heck, even if they are), even if the base glyph is actually in the ligature glyph class definition.Does this make sense to others?