Re: Binarycloud and UTF

Jean-Christophe Michel schrieb:
> Manuel Holtgrewe wrote:
> 
>> Though mbstrings provides more multi byte safe functions it is not 
>> very common and if binarycloud depends on it we set the entry level 
>> pretty high (own server).
> 
> 
> We can have a branch for multilanguage, and a third one for unicode 
> multilanguage...

Ugh, I'd popose not to branch before 3.0 final or even 3.1 if we can 
avoid it.

>>  - mb_ereg_*  Ereg seems not to be multi byte safe. PREG is not UTF 
>> safe seemingly, too.
> 
> 
> False, it's since a long time (pcre version 3 I read)
> 
>> However, there seems to be a "/u" flag for unicode support. We need to 
>> investigaget there [2].
> 
> 
>  From manual:
> u (PCRE_UTF8)
>     This modifier turns on additional functionality of PCRE that is 
> incompatible with Perl. Pattern strings are treated as UTF-8. This 
> modifier is available from PHP 4.1.0 or greater on Unix and from PHP 
> 4.2.3 on win32.
> 
> So u flag is for Pattern only, and available.

Even better use.

<snip>

> And what if Indian or Chinese people want to have their events ids or 
> strings id not set in english ?

We tell them that we don't allow it for now (3.0 final) and think about 
a branch after that.

>> C.) Most configuration values should be English and use 7bit only. 
>> This means we do not need multi byte safe methods in many places.
> 
> 
> No. If we make a multibyte system, it must be safe, not guess it will 
> not receive any mb cahr :(

True. However, I think we have no need for multibyte values in 
binarycloud's base configuration. Please correct me if I'm wrong.

Regards,

Manuel


-- 
GPG key: http://www.ggnore.net/~mholtgrewe/personal/files/public_key.asc
_______________________________________________
dev mailing list
dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected]
http://lists.binarycloud.com/mailman/listinfo/dev