Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36776 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34260 invoked from network); 3 Apr 2008 06:02:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Apr 2008 06:02:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.131 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.20.131 c2bthomr13.btconnect.com Received: from [213.123.20.131] ([213.123.20.131:23151] helo=c2bthomr13.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6E/9D-17876-0E274F74 for ; Thu, 03 Apr 2008 01:02:09 -0500 Received: from [127.0.0.1] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by c2bthomr13.btconnect.com with ESMTP id AQY07992; Thu, 3 Apr 2008 07:02:05 +0100 (BST) Message-ID: <47F47360.8040606@lsces.co.uk> Date: Thu, 03 Apr 2008 07:04:16 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: PHP internals References: <47F463F0.4030407@zend.com> In-Reply-To: <47F463F0.4030407@zend.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090207.47F472DE.0025,ss=1,fgs=0, ip=127.0.0.1, so=2007-10-30 19:00:17, dmn=5.4.3/2008-02-01 X-Junkmail-IWF: false Subject: Re: [PHP-DEV] intl naming From: lester@lsces.co.uk (Lester Caine) Stanislav Malyshev wrote: > Hi! > > I wanted to ask the people here for opinions on the subject of functions > naming in pecl/intl (hopefully soon to be ext/intl ;) module. Current > state can be seen at http://docs.php.net/manual/en/book.intl.php I suppose the main question here is the simple one. Will PHP6 be integrally - unicode? Personally I WANT a clean character set free base to work from and that is what I was under the impression that PHP6 was going to provide. If the core is running unicode ( and I see no logical reason why it should run anything else - use PHP5 for an 'ascii' based version ) then why are we discussing separating out functions which are part of that core. The core objects should properly handle unicode, so why have DUPLICATE functions such as Date and DateFormatter at all? Number and possibly Currency should also exist in the same way as Date? Collation is as much part of database handling as array, and upper and lower functions are not being moved TO intl so why should there be different handling of things. I had expected to be running PHP6 in a clean UTF-8 mode by now, and that functions like localeconv would simply work. If that is not the intention for PHP6 then perhaps we need to start looking to a replacement of PHP6 already :( -- Lester Caine - G8HFL ----------------------------- Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact L.S.Caine Electronic Services - http://home.lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php