Mail Archives: cygwin/2009/09/28/12:16:53
On Sep 29 01:03, IWAMURO Motonori wrote:
> 2009/9/27 IWAMURO Motonori <deenheart AT gmail DOT com>:
> >> LANG="ja" -> EUCJP
> >> LANG="ja_JP" -> EUCJP
> >
> > Hmmm, It is a difficult problem.
> >
> > I think selecting UTF-8 is good because eucJP is legacy.
> >
> > But, for interoperability with other UNIX-like system(*), I don't
> > think selecting UTF-8 is good.
> >
> > * Solaris: ja, ja_JP -> eucJP
> > * Linux (Debian): ja -> Unknown, ja_JP -> eucJP
> >
> > I need to think more...
>
> My conclusion is as follows as a result of hearing other Japanese
> people's opinion:
>
> LANG=ja -> UTF-8
> LANG=ja_JP -> UTF-8
>
> Because, we specify "eucJP" explicitly when we need it.
Hmm.
That's an interesting point.
In theory this sounds like a good idea to be used for all locales which
don't specify the charset explicitely, because that results in using the
same charset, "UTF-8", for all such locales. "C", "ja" or "en_US"
would all default to UTF-8.
The downside is that a user, who needs to work under the default ANSI
codepage for some reason, has to know the name of the default ANSI
codepage. Right now any user who needs the default ANSI codepage can
simply set LANG to some language code and go ahead, without having to
know the number. With your solution, that wouldn't be possible anymore
and the user would have to figure out the default ANSI codepage on the
system before being able to use it.
I honestly don't know if that's really a problem, though. But I don't
want to take that feature away for now. Anybody having a strong opinion
on this issue?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -