On Mon, 31 Mar 2003, Tomohiro KUBOTA wrote:
> Now brief list of examples. > > - Text editors which run on terminal rarely supports i18n. Emacs and > Vim are precious exceptions. What about Mined (http://towo.net/mined/) ? I have not personally used this editor. According to the documentation, "Mapping tables for Greek, Cyrillic, Hebrew, Arabic are preconfigured (tables are the same as used by the yudit editor)". If Mined uses the same tables as Yudit, then there is the possibility of easily supporting many more keyboad mappings as Yudit does already. > - Xterm. Its terminfo "enacs", "smacs", and "rmacs" (used for line- > drawing characters) assumes that G1 is not used and GR is G2, which > conflicts with EUC encodings. This causes usage of line-drawing > causes all Hiragana/Katakana/Kanji to mojibake. I proposed to > change definition of these terminfo items but it wasn't accepted > because of vague uneasiness on compatibility. I have not read any > concrete compatibility problem. > - Xterm. It can automatically use UTF-8 mode and luit depending on > locale. However, though it automatically use UTF-8 mode, it cannot > use iso10646-1 font automatically. My patch to do this (and the > idea itself) was rejected. Usage of iso10646-1 font as default > was also rejected. What about mlterm (http://mlterm.sourceforge.net/) ? mlterm has support for RTL scripts like Arabic, correct rendering for Thai, and also Indic scripts which I believe xterm does not yet have. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
