I think that the problem is caused by --enable-mbstr-enc-trans option and is not caused by mbstring itself.
If --enable-mbstr-enc-trans is enabled, php_treat_data, the original handler of user input (POST/GET/Cookie), is overrided by mbstr_treat_data in ext/mbstring , the multibyte enabled version. mbstr_treat_data had a GET handling bug in PHP 4.2.x/PHP 4.1.x. Although the bug was already fixed in CVS, but mbstr_treat_data is not used by non multibyte user. So, I abolished --enable-mbstr-enc-trans option in CVS, and made a new php.ini option 'mbstring.encoding_translation', which is the equivalent of --enable-mbstr-enc-trans, and which is 'Off' by default. I think the user input (POST/GET/Cookie) related problem for non-multibyte user will completely disappeer with this change. And, the mbstring should be 'enabled' by default. I18N of PHP is very important for especially multibyte PHP users. The core part of mbstring is stable and is widely used. In Japan, PHP has already large user community. More than 20 PHP related books were published in japanese, and there are more than 5,000 subscibers in japanese php-user mailing-list. And PHP 4.3.0 will introduce Chinese, Korean (and Russian) support in mbstring. mbstring will more widely used by non singlebyte PHP users in near future. I agree with Zeev, the simplicity of development work is important. So, the duplicate code of the user input handler should be merged with the original handler in PHP 5.0. Rui On Sun, 1 Sep 2002 10:49:59 +0100 [EMAIL PROTECTED] (James Cox) wrote: > Phil Copeland @ redhat pointed me at this bug: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=72752 > > Seems that there are a number of issues (i'm going to verify & patch his > fixes right now). > > The other he mentions is mbstring seems to cause problems. I have > experienced this too. > > Guys, i don't want to be mean or sound racist or anything else you throw at > me. > > But mbstring really isn't a core module, and very few people will require > kr/zh/ru style encoding. > > I vote to remove mbstring as a default module. > > And for those who say that i could just disable it -- well, the converse is > true. Let us STOP burdening default builds with crap that is unlikely to be > used. > > -- james -- ----------------------------------------------------- Rui Hirokawa <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
