Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47212 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64768 invoked from network); 13 Mar 2010 03:58:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Mar 2010 03:58:10 -0000 Authentication-Results: pb1.pair.com header.from=mozo@mozo.jp; sender-id=permerror Authentication-Results: pb1.pair.com smtp.mail=mozo@mozo.jp; spf=permerror; sender-id=permerror Received-SPF: error (pb1.pair.com: domain mozo.jp from 74.125.92.24 cause and error) X-PHP-List-Original-Sender: mozo@mozo.jp X-Host-Fingerprint: 74.125.92.24 qw-out-2122.google.com Received: from [74.125.92.24] ([74.125.92.24:11585] helo=qw-out-2122.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2D/B4-13686-05D0B9B4 for ; Fri, 12 Mar 2010 22:58:09 -0500 Received: by qw-out-2122.google.com with SMTP id 3so657279qwe.59 for ; Fri, 12 Mar 2010 19:58:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.127.97 with SMTP id f33mr1569348vcs.167.1268452685240; Fri, 12 Mar 2010 19:58:05 -0800 (PST) In-Reply-To: References: <4B9926E8.4080202@lerdorf.com> <7f3ed2c31003120958w7bd41059o88869669c6f5b0d9@mail.gmail.com> Date: Sat, 13 Mar 2010 12:57:45 +0900 Message-ID: To: Derick Rethans Cc: Hannes Magnusson , Rasmus Lerdorf , PHP Developers Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] PHP 6 From: mozo@mozo.jp (Moriyoshi Koizumi) Huh? mbstring has been capable of handling lots of encodings other than UTF-8 since it was introduced. We might often find it annoying that Unicode is handled transparently through I/O functions when the internal encoding is different from the outside encoding. It just seems you didn't ever make a serious internaltionalized application. Moriyoshi On Sat, Mar 13, 2010 at 3:34 AM, Derick Rethans wrote: > 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 >