|
Boost : |
Subject: Re: [boost] Fw: [locale] Formal review of Boost.Locale library
From: Ryou Ezoe (boostcpp_at_[hidden])
Date: 2011-04-14 17:15:46
For exmaple, one Japanese may write
translate("ã")
MSVC use shift-jis for encoding.
In the same time, one korean may write
translate("ê¶")
which i think(i don't know korean) MSVC use KS X 1001 for encoding.
In binary level, this is same.
What should we do?
Using string literal with no prefix is practically dangerous.
On Fri, Apr 15, 2011 at 6:01 AM, Ryou Ezoe <boostcpp_at_[hidden]> wrote:
> On Fri, Apr 15, 2011 at 5:55 AM, Artyom <artyomtnk_at_[hidden]> wrote:
>>> well, except last שָ××Ö¹× ×¢×Ö¹×Ö¸× part.
>>
>>
>> Because the sources are in UTF-8 ;-) and it is "Hello World" in Hebrew
> It can be UTF-16 as wel.
> It's just other encoding can't represents hebrew characters.
>
>> (with vowel marks)
>>
>> :-)
>>
>> The best is just to use UTF-8 (source code) anywhere - MSVC handles it
>> just fine...
> I agree with that part.
>
> But the point is string literal with no encoding prefix is evil.
> if i write
>
> char s[] = "ããããã" ;
>
> MSVC use shift-jis encoding.
>
> Japanese will sure to write something like translate("æ¥æ¬èª").
>
>
>>
>> Artyom
>> _______________________________________________
>> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>
>
>
> --
> Ryou Ezoe
>
-- Ryou Ezoe
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk