On Thu, 21 Dec 2000, Noriyuki Soda wrote:

> Huh?
> Only meaningful objection I've heard is a problem about 
> multi-thread multi-locale program.

Yep. Also, the elegance issue.

And there is another issue, that en_US.UTF-8 may have a different fontset
than zh_CN.UTF-8 and ja_JP.UTF-8 - if we just do

 setlocale(en_US_UTF8_locale),

you effectively break locales which need a different fontset than
en_US. (I suppose I have no need to tell you about the CJK font style
variations)

> And as I already said, the Xutf8 API doesn't solve the problem. 
> The only option to solve this problem is to make (very few) APIs
> which have explicit locale argument.

That is an option, certainly.  Have you got a patch to do that?

> In other words, Xutf8 APIs don't solve real problem, don't add 
> any new feature, only add incompatiblity and make code bloat.

Bruno, how big is it, a couple of kilobytes or something?  That's little
enough that it might not actually increase the memory footprint.

-- 
Robert