On Sat, 20 Nov 2010, Bill Moseley wrote:
We use Locale::Maketext in a web application (with language classes like
MyApp::I18N::en_us) and when a user selects a language a Locale::Maketext
handle is created for the request. We also call DateTime->DefaultLocale(
$tag ) to localize formatted dates.
What happened was our translators added a new language file that didn't use
the correct language code, so that's when we saw the "Invalid locale name or
id" error. That was fixed by just renaming the language file so the correct
code was used. At least it made DateTime not throw an error.
But that made me wonder if there was anything additional required to support
the new languages on the server -- or if the fact that DateTime didn't
complain about the locale was enough. I.e. does our translation team need to
notify the team that manages the servers when a new language is added.
If there is a locale in DateTime::Locale for the id, then it will provide
the same set of datetime localization information as any other locale.
Does that answer your question?
-dave
/*============================================================
http://VegGuide.org http://blog.urth.org
Your guide to all that's veg House Absolute(ly Pointless)
============================================================*/