On Thu, 17 Oct 2002 [EMAIL PROTECTED] wrote:
> > > It would be yet simpler to eliminate all non-utf-8 locales.
This is what RedHat 8.0 does except for CJK for which still legacy
encodings are used.(well for zh_CN, GB 18030 is used, which is just
another UTF in a sense.) The exclusion of CJK in a switch-over to
UTF-8 is very unfortunate (I've been using ko_KR.UTF-8 for over
half a year and I really like it) and I hope it'll change soon
(see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75829) As I
wrote many times before, Korean desperately needs UTF-8 and that's why
ko_KR.UTF-8 was among the very few UTF-8 locales offered for Solaris
and AIX (see Ienup's message.) in mid-1990's.
> > It would be "simpler", but since the vast majority of the world is still
> > using legacy locales, it's irrelevant. Come back in 5-10 years, maybe;
> > I'm talking about things that can be done today.
>
> They could still be available, but they would not be the default
> (legacy encodings)
>
> When you setup a new machine, its not front-loaded with scads
> of text file docs you care about; you will add things as you go.
> If you recieve new messages (email,documents,etc) they would
> all be converted to something you can read normally. All you care
> about is that it is well integrated and it works.
I totally agree with you.
Jungshik
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
