Emit table GDEF with GlyphClassDef and LigatureCaretByPos statements
See original GitHub issueWhen glyphsLib produces UFO for a font with ligature caret positions, the generated features.fea
should contain a table GDEF
block with LigatureCaretByPos
statements. Originally, I planned doing this in ufo2ft but that seems the wrong place; see also https://github.com/googlei18n/ufo2ft/issues/91.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Emit table GDEF with LigatureCaretByPos statements #91
Actually, should the table GDEF statement really be generated by ufo2ft? Just wondering because this logic sounds quite specific to Glyphs.app, whereas ufo2ft ......
Read more >Source code for fontTools.feaLib.parser
By default, the parser will follow ``include()`` statements in the feature file. ... languagesystem, lookup, markClass, " 'table, or glyph class definition, ...
Read more >GDEF — Glyph Definition Table (OpenType 1.9) - Typography
The Glyph Class Definition (GlyphClassDef) table identifies four types of glyphs in a font: base glyphs, ligature glyphs, combining mark ...
Read more >afdko - PyPI
table GDEF { GlyphClassDef ,,,; } GDEF;. is a valid statement. You just need to provide all three commas and the final colon...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here’s the logic of Glyphs.app, summarizing a discussion thread on this bug for reference:
Guess we can close this. Please file another bug (with a concrete example) if I’m wrong.