Open silmeth opened 1 year ago
Also a comparison between nvim-qt and Kate with a non-monospaced font that has dedicated glyphs for the insular g/d + dot combinations, Junicode Two Beta (the spacing is bad, but it also shows that the combining character doesn’t get displayed even if the font has a dedicated glyph for the combination; I don’t think I have a mono font with those glyphs):
nvim-qt:
Kate:
And a font without dedicated glyph or positioning info, but which handles the dot better than Noto Mono – GNU Unifont: nvim-qt: Kate:
Tested with a fresh build of master too, same results.
NVIM-QT v0.2.18.9999
Build type:
Compilation: -Wall -Wextra -Wno-unused-parameter -Wunused-variable
Qt Version: 5.15.8
Environment:
nvim: nvim
args: --cmd let &rtp.=',/home/silmeth/nvim-qt-new/runtime' --cmd set termguicolors
runtime: /home/silmeth/nvim-qt-new/runtime
Moreover, in this version I get weird results with the Noto Mono font with :GuiRenderLigatures 1
(doesn’t affect other fonts though):
When using combining characters in a buffer, only the base character is displayed and the combining diacritic isn’t. This doesn’t depend on the font used.
Here is a sample text I tested it on:
This is how nvim-qt displays it: and here the same text displayed in Kate:
both using Noto Mono font, size 12pt (
:GuiFont Noto Mono:h12
in nvim).As you can see, Kate displays the combining tilde over u, and the dots over insular g characters.
If the dedicated codepoint for a letter with diacritic (ũ) is used, then nvim-qt correctly displays the diacritic: and I’d expect the ⟨u⟩ + ⟨◌̃⟩ sequence to be displayed the same way (and other combinations that don’t have a dedicated codepoint, but might have glyphs in the font, to also be handled somehow and not just lose the combining character).
Neovim-qt version: