Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84118 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59993 invoked from network); 1 Mar 2015 20:34:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Mar 2015 20:34:31 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:52564] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 86/11-53678-6D773F45 for ; Sun, 01 Mar 2015 15:34:31 -0500 Received: (qmail 27783 invoked by uid 89); 1 Mar 2015 20:34:27 -0000 Received: by simscan 1.3.1 ppid: 27775, pid: 27779, t: 0.0734s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 1 Mar 2015 20:34:27 -0000 Message-ID: <54F377D2.7030601@lsces.co.uk> Date: Sun, 01 Mar 2015 20:34:26 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <1413875212.2624.3.camel@localhost.localdomain> <54469840.3070708@sugarcrm.com> <1414051917.2624.35.camel@localhost.localdomain> <1414060726.2624.60.camel@localhost.localdomain> <1414072403.3228.3.camel@kuechenschabe> <87D717D5-273B-4A32-A3E5-83EBDFD314CB@ajf.me> <1414077690.3228.12.camel@kuechenschabe> <54495CF6.30608@sugarcrm.com> <1414130585.2624.64.camel@localhost.localdomain> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] UString From: lester@lsces.co.uk (Lester Caine) On 28/02/15 06:48, Joe Watkins wrote: > This is just a quick note to announce my intention to ready this RFC > for voting next week. Since there is nothing in this which needs any changes to the core then surly it simply needs to exist in pecl until such time as a proper replacement for unicode in core strings has been addressed? Since it will still require intl to provide those areas it does not support, and I question if we really need to provide yet another encoding converter. A unicode string handler that just handles UTF8 strings may be yet another stepping stone, but it still falls short of beings able to handle all of the internationalization problems and is simply an alternate to mbstring so one either runs both, or sit down and convert all the third party libraries to eliminate mbstring. Like http extension, it's not essential that it's loaded by default, and leaving it in pecl allows development outside that of the core? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk