Hi,
I found a severe problem in 'xterm' terminfo definition.
It defines alternate character set-related capabilities like:
enacs=\E)0
smacs=^N
rmacs=^O
which are indeed using G1 of ISO-2022. This works well for 8bit
encodings which use G0 and G2. However, G1 is used in several
encodings such as EUC-JP and EUC-KR. Thus, using these terminfo
capabilities will overwrite the initial settings of G1 in these
encodings and break proper displaying. This is a real problem in
xterm+luit, though it doesn't matter for legacy xterm because it
doesn't support EUC encodings. For example,
$ xterm -u8
$ export LANG=ja_JP.eucJP
$ luit
$ dialog --msgbox foobar 8 10
$ cat Japanese_File_in_EUC
will display the contents brokenly.
The root of this problem is the definition of terminfo capabilites
of enacs, smacs, and rmacs which conflicts with EUC encodings.
How can we change the definition?
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://www.debian.or.jp/~kubota/
"Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
