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
Describe the bug
When parsing the Glyph Data of the fonts in the ufl folder, there are glyphs where the Component Glyph Flags are set to 0x236. However, according to the specification, the bits given by 0xE010 are reserved, which making bit 4 contain an invalid value.
To Reproduce
Check the fourth bit in the Component Glyph Flags. For instance, using fonttools:
Describe the bug
When parsing the Glyph Data of the fonts in the
ufl
folder, there are glyphs where the Component Glyph Flags are set to 0x236. However, according to the specification, the bits given by 0xE010 are reserved, which making bit 4 contain an invalid value.To Reproduce
Check the fourth bit in the Component Glyph Flags. For instance, using
fonttools
:Here one should note that it is not 0x236 but 0x214 because of this “cleaning” conjunction:
_g_l_y_f.py#L1419-L1421
When printing the original value there, one gets 0x236.
Expected behavior
Bit 4 should not be set.
The text was updated successfully, but these errors were encountered: