(the last screenshot shows that the new character is drawn twice:
once at its original position, and once one to the right). The file I
used for testing is attached.
FWIW, it's in utf8.
--~--~-~--~~~---~--~~
You received this message from the vim_dev
Hi Bram,
On 9/11/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
[...]
Ehm, are you just guessing here? You better find a way to test it.
I don't want to include this without testing.
I doubt X11 uses UTF-16, that is something that MS-Windows uses. GTK
uses utf-8 in most places. Other X11
Edward L. Fox wrote:
On 9/11/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
[...]
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.
Do you mean this?
Yes.
--
MORTICIAN:What?
CUSTOMER:
Edward L. Fox wrote:
On 9/11/07, Edward L. Fox [EMAIL PROTECTED] wrote:
Hi Bram,
On 9/11/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
[...]
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
Hi Bram,
On 9/11/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
[...]
Only two bytes are put in buf[], thus more needs to be changed here to
make it work.
[...]
Here too.
[...]
I don't know how to deal with the characters outside BMP for XChar2b.
I just assume that it is UTF-16. Please
Edward L. Fox wrote:
On 9/11/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
[...]
Only two bytes are put in buf[], thus more needs to be changed here to
make it work.
[...]
Here too.
[...]
I don't know how to deal with the characters outside BMP for XChar2b.
I just assume
Bram Moolenaar wrote:
[...]
I doubt X11 uses UTF-16, that is something that MS-Windows uses. GTK
uses utf-8 in most places. Other X11 toolkits probably differ, since
they are older.
Even with UTF-16, it is possible to display codepoints outside the BMP (up to
U+10 IIRC, and the
Hi Tony, thanks for your reply! But we are not talking about the
coverage of UTF-16, we just want to make sure whether X11 uses
UTF-16, or only UCS-16, which only supports BMP. I'm afraid I'll have
no time to test that until this Thursday, so I hope any one could
help. Best regards, Edward Fox
Sorry to awake this old thread...there was a newer thread requesting
correct display of unicode chars = 0x1, 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
