Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45151 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7549 invoked from network); 30 Jul 2009 17:37:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jul 2009 17:37:43 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.117 us-mr1.zend.com Linux 2.4/2.6 Received: from [63.205.162.117] ([63.205.162.117:41482] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 84/53-25953-56AD17A4 for ; Thu, 30 Jul 2009 13:37:42 -0400 Received: from us-gw1.zend.com (us-ex1.zend.net [192.168.16.5]) by us-mr1.zend.com (Postfix) with ESMTP id DE830E1242 for ; Thu, 30 Jul 2009 10:25:41 -0700 (PDT) Received: from [192.168.16.202] ([192.168.16.202]) by us-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 30 Jul 2009 10:38:07 -0700 Message-ID: <4A71DA47.8080809@zend.com> Date: Thu, 30 Jul 2009 10:37:11 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Moriyoshi Koizumi CC: php-dev References: <4A6C6496.7060603@mozo.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Jul 2009 17:38:07.0276 (UTC) FILETIME=[7FC446C0:01CA113C] Subject: Re: [PHP-DEV] Re: Alternative mbstring implementation using ICU From: stas@zend.com (Stanislav Malyshev) Hi! > Aren't there any interests on this? If you think PHP 6 is gonna cover > all of the functionality that allegedly-cruft mbstring currently > provides, that is almost wrong :-p Could you please explain why PHP6 doesn't provide what mbstring is doing? I.e, let's go over the functions: mb_parse_str - since detecting encoding doesn't work per RFC, what is the usefulness of this function? Wouldn't PHP 6 do the same with correct charset? mb_str* - shouldn't you in 6 just convert them to unicode and do all string operations with Unicode strings? Also, in 5 isn't there some intersection with grapheme_* functions? mb_output_handler - shouldn't setting the proper encoding in 6 do the same job? mb_convert_encoding - don't we already have a number of functions that do encoding conversions? -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com