Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36896
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.178 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=VLnAKMZsy1cdZo6zMoyqaV/jrkdNybivOU3twk0DrzIrm85RBu/1XaRuDp5BFQr9mtHfgO41DhscJTqYuxv0Y3iFQLNAiy/n4UJBG3cIUkMh6X2pY88PYMENLsVnYv99lTwidlr9CcW/RnN7l9Le/qM9UzPzmYJ5dpyKLaS+ULc=
Message-ID: <fe05d1540804090021w49e9366dw13dfb5945fd54550@mail.gmail.com>
Date: Wed, 9 Apr 2008 09:21:13 +0200
To: "=?ISO-8859-1?Q?David_Z=FClke?=" <dz@bitxtender.com>
Cc: "Stanislav Malyshev" <stas@zend.com>, "Andi Gutmans" <andi@zend.com>, 
	"Lester Caine" <lester@lsces.co.uk>, 
	"PHP internals" <internals@lists.php.net>
In-Reply-To: <714D4F57-DCC8-4F02-8E43-7468B99D2651@bitxtender.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <47F463F0.4030407@zend.com>
	 <698DE66518E7CA45812BD18E807866CE0175729A@us-ex1.zend.net>
	 <fe05d1540804080541l732875cv8d9f5b7e22aacc06@mail.gmail.com>
	 <47FBA5A7.1070600@zend.com>
	 <fe05d1540804081140q3fd5a0a8rcb2d0b93a066a531@mail.gmail.com>
	 <47FBBF0F.4080505@zend.com>
	 <fe05d1540804081209l68916e9ey4b0a68bec255f7e1@mail.gmail.com>
	 <9E824A53-4FF3-4BA7-84DD-C6D7A875FCB8@bitxtender.com>
	 <fe05d1540804082348i370c0da4r5c9a2ab8a2b2b6f2@mail.gmail.com>
	 <714D4F57-DCC8-4F02-8E43-7468B99D2651@bitxtender.com>
Subject: Re: [PHP-DEV] intl naming
From: pierre.php@gmail.com ("Pierre Joye")

On Wed, Apr 9, 2008 at 9:01 AM, David Z=FClke <dz@bitxtender.com> wrote:

>  Sure, but you need to remember that this means someone has to maintain t=
he
> mappings.
>
>  Mind you that pretty much any locale-related information is in the CLDR
> already - language, territory and timezone mappings, for instance.
>
>  Be advised that attempting to map, for instance, a country code to a loc=
ale
> is futile anyway. You can't map "ch" to anything. There's de_CH, fr_CH an=
d
> it_CH locales to choose from. Locales and country/language/blah codes rea=
lly
> are differnt things, and I've never needed automated mappings so far
> (usually, the locale code itself is more than enough).

Thanks for the advice :) However I already know that and to use
incomplete code as a mapping key (or whatever else) is not the goal (I
don't think I ever mentioned this idea).

To have the ISO lists, the list of available locales (to be
interpreted carefully), or do some basic operations on the locales is
what I like to have. The ICU Locale API is very complete, it can be
misused (there is many things that can be mishandled in PHP), why
should we not have it in PHP?

Cheers,
--=20
Pierre
http://blog.thepimp.net | http://www.libgd.org