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
It looks like the issue is with OpenType and how it parses certain kinds of .tff fonts, which are mapped using a cmap3 method. Those font are currently still not supported by OpenType.
There are some related issues here and here.
@Guillaume-Levrier My bad if that wasn't clear. So, we use the OpenType library to parse font data for the glyph paths. OpenType doesn't currently support certain kinds of .ttf and for the moment at least we can only support what OpenType supports.
It was reported that non-latin glyphs are being dropped and result in improper output for typefaces that include other glyphs.
To reproduce, visit the Noto Sans Page and input one of these glyphs.
The text was updated successfully, but these errors were encountered: