Hi, My wonder is how wcwidth() can give the right value with SCW. There is one more problem with wcwidth(). It does not work well for remote terminal. This is because wcwidth() is controlled by remote system (OS and library) while the actual width is determined by local system (terminal). SCW cannot solve this problem. I think something is needed to solve this problem. Otherwise, two standards of wcwidth() and SCW will conflict each other. I think it is possible. For example, application softwares can know the size of the terminal (ex. 80x24). However, it is nonsense that terminals will send the width information for all UCS characters on invocation. Thus, how about having a few modes? I imagine 4 modes, (1) UAX#11 (Ambiguous=singlewidth) (2) UAX#11 (Ambiguous= doublewidth) (3) everything is singlewidth (4) everything is double- width. OS can use this information for wcwidth(). Note that UAX#11 is not yet free from bugs and may be changed in future. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ "Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/ - Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
