Re: X input methods for utf-8?

[Ienup Sung <ienup.sung@xxxxxxxxxxx>]

Hi,

What I meant by 'The "much better" in that context...' is that if you
have a properly internationalized application (that is, by using X I18n
functions calls like Xmb/wcDrawString, Xmb/wcLookupString and so on)
then your application will work on any kind of locales/codesets including
UTF-8. And thus, you can use that same, a single binary of the application
under Japanese Shift JIS locale, Japanese EUC locale, Japanese UTF-8 
locale and so on. And, thus and since that properly internationalization can
input and output UTF-8/UTF-32, there is no reason to run an application with
Japanese Shift JIS and do iconv to input and output UTF-8/UTF-32 if
the only characters that you are going to input and output is UTF-8/UTF-32.

In other words, the key point that I'm trying to say is, "the proper
internationalization will make your application ready for any kind of
locales/codesets and UTF-8/UTF-32 is just a codeset (MB and WC) that can be
supported by such properly internationalized application without any
special modification to the already internationalized application."

And, at the sametime, as I also pointed out in several occasions, I also see
and certainly believe that there are cases that a single application would
want to input and output more than one codeset text data preferably one of
them in UTF-8/UTF-32 and in that case, such application would require to
have some level of code conversions in it hopefully through iconv(3C) as
the current APIs are not really covering all such needs and also not so
convenient to do such programming.

These are the two ideas that I've been talking about quite some over here
and other mailing lists in these days and I believe you also agree to
those points, right?

With regards,

Ienup


] Date: Tue, 30 Jan 2001 18:12:24 +0900
] From: Tomohiro KUBOTA <tkubota@xxxxxxxxxxx>
] Subject: Re: X input methods for utf-8?
] To: linux-utf8@xxxxxxxxxxxxxxxxxxxx
] MIME-version: 1.0
] Mail-Reply-To: tkubota@xxxxxxxxxxx
] 
] Hi,
] 
] At Mon, 29 Jan 2001 11:55:49 -0800 (PST),
] Ienup Sung <ienup.sung@xxxxxxxxxxx> wrote:
] 
] > Also, as I pointed out so many times in Xutf*() discussions,
] > I also think and believe that each user has freedom of choosing whatever
] > codeset and locale that he or she wants to use with his/her applications
] > that nobody dare can dictate and we also shouldn't force them to choose
] > any one codeset/locale.
] 
] Yes, I fully agree with this point.  Then why do you think as below?
] 
] > The "much better" in that context was the client programs won't need to
] > do any iconv(3) stuff if your input and output will be only in UTF-8.
] 
] I think there must not any software which can work only with UTF-8,
] because such a software is bad one, just as 8bit-only softwares or
] EUC-only softwares are bad.
] 
] Thus, we need not think about softwares whose I/O will be only in UTF-8.
] 
] 
] ---
] Tomohiro KUBOTA <kubota@xxxxxxxxxx>
] http://surfchem0.riken.go.jp/~kubota/
] "Introduction to I18N"
] http://www.debian.org/doc/manuals/intro-i18n/
] -
] Linux-UTF8:   i18n of Linux on all levels
] Archive:      http://mail.nl.linux.org/lists/
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/