In this case i suggest we wait for 4.3 branch and develop new
mbstring in head after branch.

marcus

At 02:50 04.08.2002, Yasuo Ohgaki wrote:
>Marcus Börger wrote:
>>At 10:38 03.08.2002, Yasuo Ohgaki wrote:
>>
>>>Marcus,
>>>
>>>Don't forget to create patch against development version :)
>>>cvs.php.net is _NOT_ for development new encoding/feature.
>>>
>>>http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/php-i18n/
>>>
>>>--
>>>Yasuo Ohgaki
>>
>>O.k. when i am through i will commit changes to cvs.php.net and
>>then to php-i18n. But tell me where is the need for developing that
>>part externally? IT only makes development complicated because
>>there are to diverging versions of php...
>>marcus
>
>I agree. We might create new branch for new mbstring.
>New filter is great, but it's not stable enough and
>we don't have much time since there will be 4.3.0
>soon.
>
>Currently, it works. However,there are problems in
>the filter, newer encodings are not ported, etc.
>
>Your help is very appreciated :)
>
>--
>Yasuo Ohgaki


--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to