Hiho.
> Ok, I didn't know that ISO-639-3 contained even more languages. But I
> still think unless there is a strong need to support some really obscure
> language right now the project is better of using the convention used by
> most OSS project for now (GNU, GNOME etc..).
Okay. First of all, there are no 'obscure' languages out there. One of
the goals of the ISO-639-3 was to have a code for every language out
there. To also make them equal to each other, what also means no
language is 'obscure'.
> I'm sure someone will
> eventually figure out how to extend the current convention to support
> language 451-6900 if there is indeed not supported already.
Yes, there is someone. It is called ISO-Standard-Group and the way to do
that is to use the ISO-639-3. WOW, genius!
> Sure. Message catalogs can be loaded individually. But the high-level
> api assumes that a standard
> "locale/language_TERRITORY/LC_MESSAGES/domain.mo" directory structure is
> used. The gettext module is actually used by Babel internally for this
> stuff anyway...
>
> But keep in mind that this only provides a message catalog. To get
> access to the CLDR locale database
> a language id is not enough, you need to know the territory as well.
>
> A sneak preview :)
>
> >>> import babel
> >>> babel.Locale('de_DE').languages['sv']
> u'Schwedisch'
> >>> babel.Locale('de_DE').languages['nai']
> u'Indianersprachen, Nordamerika (Andere)'
>
> Cheers,
> Jonas
maybe we should discuss that (because I didn't get the example anyway),
when we are discussing about a new translation system anyway (what, so
was your suggestion are we going to do soon, when we are thinking about
a tv schedule).
I wrote an explaining document and going to upload it into svn soon. But
I'm not here to argue about the benefits or usage of babel.
benjamin
