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
The bowl glyph (3rd to last glyph in font) is inconsistent in width and shape across the superfamily: It has a width of 1230 in Argon and Neon, 1240 in Krypton, empty glyph of width 600 in Radon and not present in Xenon. The inconsistency of width has caused issues especially when combining with CJK fonts, where in Linux fontconfig the monospace attribute is determined as the whole font having at most 3 different values of widths (including zero width), which the inconsistent bowl glyph makes the font not monospaced.
[Also it should be noted that Xenon has a total glyph counts of 832 which is more than the rest of the superfamily of 779-783 which makes the coverage across the superfamily slightly more inconsistent]
The text was updated successfully, but these errors were encountered:
Hi, thanks for pointing this out! The bowl glyph is actually used in our production (ensuring letters like b/d/p/q have matching bowl shapes), and shouldn't have been exported in the final fonts. The next version of the fonts will have this character removed to avoid any more issues.
The
bowl
glyph (3rd to last glyph in font) is inconsistent in width and shape across the superfamily: It has a width of 1230 in Argon and Neon, 1240 in Krypton, empty glyph of width 600 in Radon and not present in Xenon. The inconsistency of width has caused issues especially when combining with CJK fonts, where in Linuxfontconfig
the monospace attribute is determined as the whole font having at most 3 different values of widths (including zero width), which the inconsistentbowl
glyph makes the font not monospaced.[Also it should be noted that Xenon has a total glyph counts of 832 which is more than the rest of the superfamily of 779-783 which makes the coverage across the superfamily slightly more inconsistent]
The text was updated successfully, but these errors were encountered: