On 09/01/02, "James Cox" <[EMAIL PROTECTED]> wrote: > mbstring isn't a "gold" module which should be enabled by default.
But there was a discussion and it was agreed to enable it by default! > That is, it's still -- as i see it -- just a bit more than experimental. > mbstring work is being done on sourceforge! Actually, thats incorrect. mbstring in PHP CVS is based on work that has matured since PHP 3. A new, rewritten version is being developed outside of our CVS so as not to screw things up for the mainstream. > So I want to 'disable' it by default. If you want encoding, just enable it. > But you're right, i've never needed to create a truely globalized/localized > app. (and from general principles, if you feel you need to localize any more > than your ui/strings.....) But the issue is not with mbstring encoding, it's with people who turn on an advanced feature without reading the docs. --enable-mbstring is on by default and works just fine. --enable-mbstr-enc-trans is the advanced option (that was causing problems for RedHat because people were enabling it without configuring it correctly for their system) - this option is DISABLED by default. Why can't we just keep it at that? Lets make a comparison: the session module has an little option called --enable-trans-sid. This option is similar to the mbstring option in question, in that it transparently converts stuff. Now, should we disable the session module by default because someone didn't read the docs and just enabled it and then complained that it was rewriting stuff?? Or how about another comparison: apache has a -DBIG_SECURITY_HOLE (or similar define) that allows it to run as root. Should they remove that option just because some idiot out there adds it to their compile options without understanding what it does? (And there *are* production systems that require this in order to function - Cobalt Raqs for example). Why can't we have the configure print a warning that the enc-trans may cause problems if it is not configured correctly for your system/application? Enabling mbstring by default was a milestone that meant that people could start writing some real-world applications because the PHP infrastructure for them was guaranteed to be there by default; don't just drop it out now because people don't read the docs. --Wez. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
