Re: [boost] [chrono] i/o to locale or not to locale

Subject: Re: [boost] [chrono] i/o to locale or not to locale
From: Artyom Beilis (artyomtnk_at_[hidden])
Date: 2011-12-10 04:31:42

I have some deadlines so I'll be able to read it deeply next Saturday and I'll gladly do it.

 
Artyom Beilis
--------------
CppCMS - C++ Web Framework:   http://cppcms.sf.net/
CppDB - C++ SQL Connectivity: http://cppcms.sf.net/sql/cppdb/


>________________________________
> From: Vicente J. Botet Escriba <vicente.botet_at_[hidden]>
>To: boost_at_[hidden] 
>Sent: Saturday, December 10, 2011 11:22 AM
>Subject: Re: [boost] [chrono] i/o to locale or not to locale
> 
>Le 12/11/11 16:58, Artyom Beilis a écrit :
>>
>> ----- Original Message -----
>>> From: Vicente J. Botet Escriba<vicente.botet_at_[hidden]>
>>>>Â   You make it too specific. Order is generally not good enough. It should
>>>>Â   be pattern not "rule"
>>>>
>>>>   1 second  ->   1秒 in Chinese (no space)
>>> You are right. The pattern will contain also<none>Â  <space>Â  as it is
>>>
>>> done for the moneypunct facet.
>> No, you are still missing my point. What if it is NBSP? What if in some
>> locale it requires some symbol before like "(" in some money?
>>
>> What I'm trying to say that you limit your self to some small set
>> of predefined cases. This is correct for some but may be not correct
>> for other cases.
>>
>> The correct is to use string pattern. This is how CLDR defines
>> localization parameters. And CLDR is **The** reference.
>The implementation uses for the moment a string pattern. I have not 
>added yet byname facets but they can be added on top of the current 
>facets. The documentation is on going (see .qbk file)
>Please could you take a look on trunk to see what could be wrong?
>
>Any other interested in an evolution of chrono i/o?
>
>Best,
>Vicente
>
>_______________________________________________
>Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>
>