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
Currently, when Kitty processes composed characters, it requires the base codepoint as well as every combination character to have dedicated glyphs in the font (see has_cell_text()), otherwise it switches to a fallback font. This is undesirable when a font has a precomposed glyph for the combination but not the individual combination chars. For instance, Roboto Mono is rather bad in this regard.
Given that HarfBuzz will try to normalize the combination anyway, we can just look for a precomposed character in the current font before giving up. Possible implementation.
The text was updated successfully, but these errors were encountered: