Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72509 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11358 invoked from network); 12 Feb 2014 10:17:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Feb 2014 10:17:11 -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:58551] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/D1-00747-42A4BF25 for ; Wed, 12 Feb 2014 05:17:10 -0500 Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 4E269E203C; Wed, 12 Feb 2014 10:17:04 +0000 (GMT) Date: Wed, 12 Feb 2014 10:17:04 +0000 (GMT) X-X-Sender: derick@whisky.home.derickrethans.nl To: Yasuo Ohgaki cc: "internals@lists.php.net" In-Reply-To: Message-ID: References: User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Re: [VOTE] Multbye char handling - Remove vulnerability related to multibyte short and long term From: derick@php.net (Derick Rethans) On Wed, 12 Feb 2014, Yasuo Ohgaki wrote: > Hi all, > > On Mon, Feb 10, 2014 at 12:56 PM, Yasuo Ohgaki wrote: > > > Long term: Alternative implementation of mbstring using ICU > > https://wiki.php.net/rfc/altmbstring > > We need multibyte feature as default. However, current mbstring has > > license issues. Resolve license issues by alternative mbstring in the > > future. Introduce mbstring-ng as EXPERIMENTAL module for further > > development, testing, feedback from users. > > All of voters other than me voted no, so far. > I would like hear the reason. The proper way to handle this is language Unicode support. Having *yet another* "UTF-8" extension is not a long term solution. cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug Posted with an email client that doesn't mangle email: alpine