Steve Hall wrote:
On Fri, 2007-01-05 at 22:30 -0700, Kenneth Reid Beesley wrote:
I've started looking at vim again, and as far as I can see, it
"handles" Unicode supplementary chars internally, but still doesn't
render them properly.
E.g. if you enter CTRL-V U00010400 the character is in the buffer,
and can be written to file, but all you see on the screen is a
question mark.
Is that still the status? or is there a way to enter supplementary
chars in vim and see the glyphs?
Vim renders Unicode just fine, but your font must support the glyph in
question or you will only see a question mark or a box.
In my experience, gVim (the GUI version) and a corresponding True Type
fonts such as Andale Mono, Courier New, Monospace, Bitstream Vera Sans
Mono, or Luxi Mono render many more glyphs than can be accomplished in
a terminal.
Steve, I think the impossibility to display Unicode codepoints above U+FFFF is
a limitation in current versions of Vim. Both my version of gvim and my
browser use GTK2+Xft to render text, and I can set the same fonts in both, but
the browser will render correctly at least some Chinese characters in the
range U+20000 - U+2FFFF and gvim won't -- only a double-width question mark is
shown.
Note that the GTK2 versions of gvim don't have the "monospace" limitation: if
the 'guifont' is not truly fixed-width, gvim with GTK2 GUI clips too-wide
glyphs to che character cell size and pads too-narrow glyphs with blank space:
it may be ugly but it shows the character is there. In the case of codepoints
above U+FFFF, all I see is a question mark, which in the case of CJK
codepoints is a "wide" question mark.
Best regards,
Tony.
