googlefonts / googlefonts/glyphsLib
Support "disabled" glyph classes
- Dominant language
- Python
- Stars
- 201
- Forks
- 56
- Avg merge
- 17m
- Merged PRs (30d)
- 1
Description
For example, features.fea in all generated UFOs has "uni0305" in "@MarkClass1" but "overlinecomb" elsewhere in features.fea and all other files.
To reproduce, run glyphs2ufo on [this file](https://github.com/psb1558/Junicode-font/blob/master/source/Junicode-Italic(bug-demo).glyphs) (Junicode Italic).
Is this a bug, or is there something odd about this file?
Contributor guide
Research direction
Reproduce the issue by running glyphs2ufo on the linked Junicode Italic(bug-demo).glyphs file. Inspect the generated UFOs' features.fea files, especially @MarkClass1, and compare the uni0305 and overlinecomb naming. Done means disabled glyph classes are handled consistently in the generated output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100