Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71620 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41086 invoked from network); 27 Jan 2014 02:54:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jan 2014 02:54:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.41 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.41 mail-la0-f41.google.com Received: from [209.85.215.41] ([209.85.215.41:54283] helo=mail-la0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/6C-12631-B6AC5E25 for ; Sun, 26 Jan 2014 21:54:36 -0500 Received: by mail-la0-f41.google.com with SMTP id mc6so4134780lab.0 for ; Sun, 26 Jan 2014 18:54:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=1Z+BFAfcOl1iHD4sZKtZdnMDXBRTMHLzWCovfUTSKzg=; b=OSzrqcRtoPNm/jMYrDWWxV+8CYEWmwYDL+dA71WEvwf3AtcTco3Gg6tTEnAh84QSdA pCYQuq7+TuafTDz3QygBI4almXhbaqXYEMLAYTUABuihQ57ocweJOp2pi4vjuerhuvUa SLhPxXe2ABYP3dq6YUmzwnTJDfSqiMJKMqi3xvPYQJoaq4WkrHcaO8nJTRza0tyKyUo1 Q/owgqNzR9s4AoQcCG5RJoCEZFlXV9zzTbgHpM6arLXrnmhvnCPIQ+iR1KCBbAu3tfNj AZ63L3JXCE7lMlKZrbkGLd5MzExWiVgdBNkGMcFgzoFaxgmAaUeWFnp56jwo2GvthPXp suXQ== X-Received: by 10.112.91.228 with SMTP id ch4mr15009737lbb.19.1390791272136; Sun, 26 Jan 2014 18:54:32 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.132.134 with HTTP; Sun, 26 Jan 2014 18:53:52 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Jan 2014 11:53:52 +0900 X-Google-Sender-Auth: yFVFEtpijFbP-vqYYv0FQ7A-RQ0 Message-ID: To: Dan Ackroyd Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11348ababb853504f0ead3ae Subject: Re: [PHP-DEV] [VOTE] RFC: Multibyte Char Handling From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11348ababb853504f0ead3ae Content-Type: text/plain; charset=UTF-8 Hi Dan, On Mon, Jan 27, 2014 at 9:09 AM, Yasuo Ohgaki wrote: > I just didn't want to touch 5 year old RFC. > As I wrote in parent RFC, the implementation is subject to be changed. > I've updated altmbstring RFC as this RFC name implies. Original author was intended to provide alternative to mbstring. In contrast, my RFC is intended to replace mbstring by mbstring-ng. There are technical difficulties to copy all of mbstring feature to mbstring-ng, we may evaluate them and decide migration procedure when mbstring-ng is ready. Choices would be - provide mbstring-ng as alternative of mbstring - keep mbstring-ng in php-src, move mbstring to PECL - keep both mbstring-ng and mbstring in php-src - replace mbstring by mbstring-ng and move mbstring to PECL as mbstring-legacy. I'm not sure which one is the best. We may try to find out by providing mbstring-ng as EXPERIMENTAL module. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11348ababb853504f0ead3ae--