You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When converting a glyph from glyphs to ufo, we zero the widths of non-spacing marks. The logic here involves finding the category and subcategory if the glyph by looking it up in the bundled GlyphData; but this lookup only uses the user-assigned glyph name, which can be arbitrary.
Elsewhere when we fetch this data (such as when building public.openTypeCategories we use the name as well as the unicode values; we should be doing the same during conversion.
(I have a patch for this I'll push in a moment, just wanted an issue to reference)
The text was updated successfully, but these errors were encountered:
cmyr
linked a pull request
Jan 23, 2025
that will
close
this issue
When converting a glyph from glyphs to ufo, we zero the widths of non-spacing marks. The logic here involves finding the category and subcategory if the glyph by looking it up in the bundled GlyphData; but this lookup only uses the user-assigned glyph name, which can be arbitrary.
Elsewhere when we fetch this data (such as when building
public.openTypeCategories
we use the name as well as the unicode values; we should be doing the same during conversion.(I have a patch for this I'll push in a moment, just wanted an issue to reference)
The text was updated successfully, but these errors were encountered: