On 01/09/02, "James Cox" <[EMAIL PROTECTED]> wrote: > The other he mentions is mbstring seems to cause problems. I have > experienced this too.
Umm, dont enable the transparent encoding support then. I don't, and I've had no problems. > But mbstring really isn't a core module, and very few people will require > kr/zh/ru style encoding. But what about all the other encodings (not just charsets)? > I vote to remove mbstring as a default module. I guess you have never tried to create a truely globalized/localized application then? I'm -1 on removing it, because PHP needs a consistent charset encoding API that is portable across platforms. iconv and recode are "no good" because their supported charsets vary from system to system and version to version; some libraries actually have broken encoding tables Enabling mbstring by default was a very good move (tm). But enabling the transparent encoding support option just because it's there is not a very good move. Just because people enable stuff they don't understand is not a good reason to disable this module. Actually, I'm -2 on removing it; -1 because PHP scripts can use it, and and additional -1 because PHP extensions that need to play with encodings can (and do) also use this portable API. --Wez. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
