Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47179 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40999 invoked from network); 12 Mar 2010 18:34:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Mar 2010 18:34:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Linux 2.6 Received: from [82.113.146.227] ([82.113.146.227:44234] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 30/8D-13686-A498A9B4 for ; Fri, 12 Mar 2010 13:34:52 -0500 Received: from localhost (xdebug.org [127.0.0.1]) by xdebug.org (Postfix) with ESMTPS id 4FB57E202A; Fri, 12 Mar 2010 18:34:36 +0000 (UTC) Date: Fri, 12 Mar 2010 13:34:29 -0500 (EST) X-X-Sender: derick@kossu.derickrethans.nl To: Hannes Magnusson cc: Moriyoshi Koizumi , Rasmus Lerdorf , PHP Developers Mailing List In-Reply-To: <7f3ed2c31003120958w7bd41059o88869669c6f5b0d9@mail.gmail.com> Message-ID: References: <4B9926E8.4080202@lerdorf.com> <7f3ed2c31003120958w7bd41059o88869669c6f5b0d9@mail.gmail.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] PHP 6 From: derick@php.net (Derick Rethans) On Fri, 12 Mar 2010, Hannes Magnusson wrote: > On Fri, Mar 12, 2010 at 17:38, Moriyoshi Koizumi wrote: > > I'd love to see my brand-new mbstring implementation in the release. > > Dropping mbstring completely won't be any good because lots of > > applications rely on it, but I don't really want to maintain the funky > > library bundled with it. > > Thats actually one of the ideas we had on IRC. > That mbstring patch and more ext/intl features should be enough to > solve "the unicode problem". Sorry, but that is not true. intl and mbstring can provide functionality to deal with UTF 8 string manipulation functions, they can not provide proper Unicode support. Proper Unicode support is *not* only just dealing with UTF-8 strings. Proper Unicode support includes dealing with file streams, with different encodings, with localiztion, with sorting, with locales, with formatting numbers. Offloading this to extensions makes Unicode support an add-on hack, and not a language feature. I am not saying that intl and mbstring aren't *useful*, but they definitely do not solve "the unicode problem". regards, Derick