[boost] Boost.Unicode (was Re: Boost.Locale)

Subject: [boost] Boost.Unicode (was Re: Boost.Locale)
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2010-12-15 09:04:46

On 15/12/2010 13:34, Dean Michael Berris wrote:
> On Wed, Dec 15, 2010 at 8:21 PM, Mathias Gaunard
> <mathias.gaunard_at_[hidden]>  wrote:
>> On 15/12/2010 01:44, Edward Diener wrote:
>>>
>>> Maybe the lack of interest is because this means little to me, and may
>>> mean little to others. If you have a library you need to tell people how
>>> to get it. I found a Soc 2009 home page and I still have no idea how one
>>> is supposed to see what is there or how to get your library.
>>
>> There have been emails about it regularly on this mailing list for the past
>> year and a half.
>>
>> Searching this list for Unicode should give you many hits.
>> The docs are here, if that's what you're looking for:
>> <http://mathias.gaunard.com/unicode/doc/html/>
>>
>
> This is just beautiful -- I think this is exactly what I need in
> cpp-netlib! Will this be submitted to Boost for review soon, because I
> really want to be able to deal with UTF-8 real soon now. :D

It could be submitted soon if I gave it a bit of love. If my talk about 
it gets accepted for boostcon 2011, I will definitely have it in the 
review queue several months before it starts.

>>> Very strange. You mention your library as possibly being more complete
>>> but then you tout someone else's. OK, I will study Artyom's Boost.Locale
>>> instead.
>>
>> My library is more powerful in a way, but is also less polished and
>> feature-complete.
>
> So, what are the features you'd like to implement so that us potential
> users can be the judge of whether it's feature-complete enough?

- I need to finish support for word, sentence and line boundaries
- The ABI needs to be more clearly defined to guarantee backward and 
upward compatibility
- The convert and segment subsystem must be clearly separated into its 
own library and namespace
- The system must be made SIMD-ready
- Simple case conversion should be added
- General case folding (and maybe collation) should be added

Nothing among these is particularly difficult.