Re: intl naming

On Wed, Apr 9, 2008 at 9:01 AM, David Zülke <dz@bitxtender.com> wrote: > Sure, but you need to remember that this means someone has to maintain the > 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 locale > is futile anyway. You can't map "ch" to anything. There's de_CH, fr_CH and > it_CH locales to choose from. Locales and country/language/blah codes really > 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, -- Pierre http://blog.thepimp.net | http://www.libgd.org