[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: non-ASCII characters in /etc/locales.alias ?

On Fri, Jan 18, 2002 at 08:33:28PM +0900, Tomohiro KUBOTA wrote:
> > | > 日本語		ja_JP.ISO-2022-JP
> > | 
> > | Hmm, I think it is not useful because we cannot input Japanese character
> > | unless configuring Japanese locale.  It is just "the key for this locked
> > | box is inside the box" situation.  (Usage of ISO-8859-1 character before
> > | definition of locale is also this situation.)

The only thing I might call "wrong" about this is just a nitpick: you
need a Japanese-capable locale, not a Japanese locale.  (en_US.UTF-8 is
fine, you don't need ja_JP.XXX.)

> BTW, the contents of your mail was illegal encoding ... It
> contained my ISO-2022-JP-encoded Japanese and your 8bit
> characters (0xe6, 0xf8, 0xe5, 0xe7), though the mail header
> insists the contents is ISO-8859-1.  Of course, ISO-2022-JP-
> encoded JIS X 0208 characters in ISO-8859-1 encoding is
> illegal.  (I imagine your 0xe6 0xf8 0xe5 0xe7 sequence in
> your mail is intended to be ISO-8859-1, I imagined from your
> mail header.  Thus, 0xe6 is "ae", 0xf8 is "o/", 0xe5 is "a"
> with circle, and 0xe7 is "c," .  What did you want to mean?)

Well, that's valid SJIS: 蹂裼.  Perhaps his shell session is set to
POSIX, but his xterm "intelligently" figures it out?  (I don't like
things doing that; it obscures problems and confuses people.)

Of course, sending SJIS to a non-SJIS locale session isn't legal.  (It'd
also explain why it didn't get sent in the mail correctly.)

Glenn Maynard

Reply to: