Handle Unicode Variation Sequences #681
Comments
|
Thanks for reminding me about the missing default UV mappings. I just fixed this. This is fully handled on export so glyphsLib can implement this properly already (using the manually set mappings from the .glyphs file and the default mappings from the Unicode data). |
khaledhosny
added a commit
that referenced
this issue
Feb 19, 2024
If a glyph name ends with ".uvNNN" with NNN ranging from 001 to 256, then it is a variation sequence with uv001 being U+0xFE00 and uv256 being U+0xE01EF. The only documentation for this is the "More Improvements" section in Glyphs 2.6.1 announcement: https://glyphsapp.com/news/glyphs-2-6-1-released And this forum post: https://forum.glyphsapp.com/t/unicode-variation-selector-u-fe00/21701 Fixes #681
khaledhosny
added a commit
that referenced
this issue
Feb 19, 2024
If a glyph name ends with ".uvNNN" with NNN ranging from 001 to 256, then it is a variation sequence with uv001 being U+0xFE00 and uv256 being U+0xE01EF. The only documentation for this is the "More Improvements" section in Glyphs 2.6.1 announcement: https://glyphsapp.com/news/glyphs-2-6-1-released And this forum post: https://forum.glyphsapp.com/t/unicode-variation-selector-u-fe00/21701 Fixes #681
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since GlyphsApp 2.6.1 Glyphs files can have some UVS support:
While this is incomplete, as it doesn't support default UVS or duplicates glyphs when it doesn't need to (see https://forum.glyphsapp.com/t/unicode-variation-sequences/11813/7), glyphs2ufo should probably do something with that data and fill in or update
public.unicodeVariationSequencesin the font.lib.The text was updated successfully, but these errors were encountered: