Hi,

In message "[ruby-talk:01040] Re: Is this a bug?"
    on 00/01/03, Yasushi Shoji <yashi / yashi.com> writes:

|hmm... wouldn't it be better if we change the word "kcode" to more
|generic term, since it's not used only for "kanji" code?

I agree with it.  I'm thinking of `encoding', because Ruby does treat
character encoding, but character set, i.e treating encoding like EUC,
UTF-8, not charset like EUC-JP, EUC-KR, nor Unicode.  SJIS is special,
because its encoding and charset are not separated.

|# I'm assuming that 'k' stands for "kanji"

$KCODE, Regexp options e,s,u,n, which is not documented in English
reference, are not generic enough for internationalization.  I added
these features to treat my everyday data (mostly in EUC-JP).  Redesign
should be needed for I18N.

							matz.