Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71201 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78772 invoked from network); 17 Jan 2014 03:20:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jan 2014 03:20:06 -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.48 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.48 mail-la0-f48.google.com Received: from [209.85.215.48] ([209.85.215.48:53001] helo=mail-la0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/11-04749-561A8D25 for ; Thu, 16 Jan 2014 22:20:05 -0500 Received: by mail-la0-f48.google.com with SMTP id er20so3156399lab.21 for ; Thu, 16 Jan 2014 19:20:01 -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=EGiysImrUTII2pQ5M1YUT4vOCHJSfZt/2iYl9tDWQs0=; b=RE5p6C103oHKt4ZdGuw9K/ky8wD8EypU+T5vUkPGKgdFT7Ls6XtU0y3aBKU4eYzKEu 8qWCPAOxDq9EzfY7YbE9Dap3DFRQw6jfkVx5ox0LzuYNMumEzVBzswsAk83mZ89aNOEi AeU8SpQjnOHmpSU4vlCICc9sg0y6HUaExNBhz4brS4IHNtuSsi8kIAKAe9XSg4TWkPvz cz2hpF2P1F/nxInA8EqT/e6anxK4++8G2xiVpaHwggstVz5ZweBShcQK+wRTJfnk903y 0RjzYAoAnKVny+Z0xm+nB13XuW67lWOJXsByYFFk3OAYrTJhEBDC0s+/y8Ze8CF5TeZV Ca3g== X-Received: by 10.152.5.199 with SMTP id u7mr2782574lau.48.1389928801261; Thu, 16 Jan 2014 19:20:01 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.6.68 with HTTP; Thu, 16 Jan 2014 19:19:21 -0800 (PST) In-Reply-To: References: <20140116023616.A43BF26437F@dd15934.kasserver.com> <52D7889D.4010705@sugarcrm.com> Date: Fri, 17 Jan 2014 12:19:21 +0900 X-Google-Sender-Auth: oUAzrlnPlfoUykG2iWwB4W1zUCw Message-ID: To: Derick Rethans Cc: Stas Malyshev , "mails@thomasbley.de" , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e013d1a78765db504f02204f0 Subject: Re: [PHP-DEV] Re: [RFC] Multibyte char handling From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e013d1a78765db504f02204f0 Content-Type: text/plain; charset=UTF-8 Hi Derick, On Thu, Jan 16, 2014 at 8:38 PM, Derick Rethans wrote: > > > We need few more basic functions like trim(). > > > This is different issue, but I may work on it. > > > > It feels like we will end up with creating clones of pretty every string > > function there is. Not sure it is the best approach... > > No, the best approach is to have "proper" unicode support in PHP, a la > "PHP 6". Then at least the duplication happens for us devs and not > users. I agree that we need to discuss encoding issue as a whole. This RFC is to eliminate known vulnerability from current implementation. Let's discuss this issue later. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e013d1a78765db504f02204f0--