Tomohiro KUBOTA <[EMAIL PROTECTED]> typed:
:I am a user of Rxvt. I use Rxvt with Japanese (kanji)-enabled since
:I am a Japanese speaker.
:I am using a Debian GNU/Linux distribution. Debian aims to be an
:internationalized distribution and has a 'rxvt-ml' package. The
:package contains 'krxvt', 'crxvt-gb', 'crxvt-big5', and 'grxvt'.
:The 'krxvt' is what I am using exactly.
:Though I don't have a skill to do that, I have a comment on Rxvt.
:Now Rxvt can handle a few special encodings. However, the encoding
:has to be specified on compile.
With rxvt 2.7.3 (2.7.1 and up, from memory), you specify multi-character
glyph support during configure (prior to compiling). Then you can
choose an encoding method at run-time, either from the command line
or via your ~/.Xdefaults (or equivalent). This means you have a single
program which supports the following encodings: "sjis" (Shift-JIS),
"eucj" (EUC JP), "gb" (GB2312), "big5", "kr" (EUC KR) and
"noenc" (no encoding (when you want latin-1 8-bit characters)).
You can also choose a default encoding method at compile time if you
are likely to only use one of those. However, there is no support to
change encoding method after running rxvt. You need start another rxvt
instance to get a different encoding method (i.e. you can't start an
rxvt window with "eucj" then decide you want "sjis" in that window).
Regards,
--
Geoff Wing : <[EMAIL PROTECTED]> Work URL: http://www.primenet.com.au/
Rxvt Stuff : <[EMAIL PROTECTED]> Ego URL : http://pobox.com/~gcw/
Zsh Stuff : <[EMAIL PROTECTED]> Phone : (Australia) 0413 431 874
