On Feb 21, 2014 4:05 AM, "Crypto Compress" <[email protected]>
wrote:
>
> Hi Pierre,
>
>> >> Thoughts, comments or ideas?
>> >
>> > it may be crazy to even think about it, but my idea is to mix the
"worst" (C++ *and* ICU) to get the ultimate unicode foundation.
>> >
>> > Boost.Locale:
>> >
http://www.boost.org/doc/libs/1_55_0/libs/locale/doc/html/rationale.html#why_icu
>>
>> Mainly because we like to use UTF-8 storage.
>>
>
> What do you understand by "storage"?
To have string stored as UTF-8 only, no conversion required for 99% of our
use.
> Quote: "U_CHARSET_IS_UTF8 allows to force ICU to use UTF-8 by default. It
is a ICU compile time setting."
> Source: Pierre
>
> Quote: "...stateless encodings like UTF-8..."
> Source:
http://www.boost.org/doc/libs/1_55_0/libs/locale/doc/html/charset_handling.html#codecvt_limitations
ICU has limitations in the utf-8 mode. To bundle UTF-8 or ask custom build
could be a problem as well. The other point to check is whether ICU can
have two installs on the sane systems, one with the flag and one without.
It could help as distros can then provide both.
>
>> Also pure c++ api is not an option yet. Unless we rewrite php in c++ but
then I would go with a 3-4 years Dev phase
>>
>
> Yes, a complete rewrite is insane not crazy. Prefer small evolutionary
steps and some bigger ones.
>
>> ...not really what I am looking for.
>>
>
> We know what you are looking for. You asked for ideas.
Maybe I was not clear here. What I am not looking for is to delay a
possible 6 release to 2-3 years later. Ideas, like yours here, are indeed
more than welcome.