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
Kitty renders incorrectly (at an incorrect smaller size) the ligatures of Cascadia Code's recently-released version 2102.03. Before this precise font version (until version 2009.22, included), Kitty used to render its ligatures perfectly.
Previously, the ligatures in Cascadia were "backwards looking", which is to say that in a three glyph run, such as >>>, the final > would contain the ligature with a negative left side bearing, and normal right side bearing.
However, [starting with version 2102.03] I changed it to be "forwards looking" which means that the first > contains the ligature as that allows me to be more efficient with my code and simplifies things quite a bit. But it appears that Kitty can't deal with that.
Steps to reproduce the behavior:
Install Cascadia Code 2102.03 (I used the static TTF version / regular+bold. I didn't try the TTFbundle or OTF versions)
Note that it works by checking how the font wants to render the ligature for === if it does it with trailing spacer glyphs, instead of leading ones then all ligatures are assumed to be with trailing spacer glyphs rather than leading ones. So please keep your ligatures consistent.