Nicolas Weber wrote:
> Sorry to awake this old thread...there was a newer thread requesting
> correct display of unicode chars >= 0x10000, but I can't find it, so I
> reply to this. Since this thread is so old, I'm quoting the whole
> thread below. Sorry if this offends you in some way ;-)
>
> I can confirm that the Mac OS X versions of vim (carbon gvim and
> console vim) display characters outside of the BMP correctly (carbon
> vim has some drawing issues, but it has those as well when it displays
> BMP double-width characters as well. If we get this going, I could
> look into that as well). I can test on win32 and ubuntu (gtk version)
> as well if there's interest.
>
> Here's a diff (which is not supposed to become an official
> patch! ;-) ) that enables displaying of characters outside of the BMP:
Thanks for looking into this. Looks good. Except that a check for
UNICODE16 is needed, if that is defined then we really can use only 16
bits.
--
GUARD #2: Wait a minute -- supposing two swallows carried it together?
GUARD #1: No, they'd have to have it on a line.
GUARD #2: Well, simple! They'd just use a standard creeper!
GUARD #1: What, held under the dorsal guiding feathers?
GUARD #2: Well, why not?
The Quest for the Holy Grail (Monty Python)
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
