Tomohiro KUBOTA writes:
>> The most URGENT thing on the to-do list is to write
>> some real code to classify a Unicode character as single-width (e.g., ASCII)
>> or double-width (e.g., Chinese characters).
>
>Did you know doublewidth/combining patch for xterm-utf8 ?
>
> http://www.wholehog.fsnet.co.uk/robert/xterm/
>
>The patch has a function my_wcwidth(). This may be helpful.
Thanks for the pointer. It uses Markus Kuhn's implementation of wcwidth()
function ( http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c ). As this is
designated as public domain by the author, I guess we can just borrow it.
>BTW, how do you think about supporting ISO2022-based encodings
>like Kterm does?
Is it possible to write a function to convert a string of ISO2022-encoded bytes
to a string of u_int16_t or u_int32_t ? (Similar to UTF-8 --> UCS2). If this
can be done, then it can be supported under my 'multibyte-char' patch
( http://www.ics.uci.edu/~xge/clinux/rxvt/ ).
-- Xianping
[EMAIL PROTECTED]
