[Localization] Peruvian Locales

[Chris Leonard]

Dear Sebastian,

The use of babel in "webby" frontends is unfortunately making this (a
requirement for both glibc locale AND CLDR locale) a more common
occurrence.

Your experience is not unique in this regard, Adam Holt and Braddock
Gaskill have encountered a similar situration with regard to Haitian
Kreyol and Internet-in-a-Box.

The long term answer is obvious (but long term).  We need to create
appropriate CLDR locales.  A CLDR locale is a bit of a combination of
a glibc locale and some additional translations of country names,
language names and other ISO-code elements.  Our existing work will be
re-used, but we will need to gather more translations.  I will work
with the localizers to gather thi sinformation for an eventual CLDR
locale submission upstream (which is a new proecss for us, so it will
take some working out).

The short term (workaround) is something you should discuss with Adam
and Braddock.  They did a slightly ugly hack to force part of the
behaviour they wanted in IIAB, although it appears to have it's
short-comings as a long term solution, AFAICT), it at least should
allow for some testing.  "Working code now".

Regards,

cjl

On Sun, Sep 15, 2013 at 2:21 AM, Sebastian Silva
<sebastian at fuentelibre.org> wrote:
> Hi fellow localizers,
>
> I've been following with excitement the recent inclusion of Aymara and
> Quechua into the core GNU C library (GLIBC),
> announced on this list. To all involved, please receive a heartfelt thank
> you.
>
> I'm developing the Sugar Network Webui which provides access to the Sugar
> Network (a "social" and decentralized repository of software, projects and
> content) over a HTML view (check out a demo at http://network.sugarlabs.org/
> ). The same interface is available with extra funcionality as a Sugar view
> on XO laptops even without Internet.
>
> Now I've found that it turns out the tools I'm using for L10n (Babel) don't
> use the locales from GLIBC but from something called the CLDR, which is a
> database mantained by the "Unicode consortium".
>
> I could only find a reference to these languages in this website:
> http://cldr.unicode.org/development/development-process/design-proposals/languages-to-show-for-translation
> where they refer to drafts of Aymara as "ay" and Quechua as "qu" instead of
> "ayc" and "quz" we've been using.
>
> I've created a bug for Babel ( https://github.com/mitsuhiko/babel/issues/55
> ) in the hopes to find a workaround but probably the best thing to do would
> be to submit these locales for inclusion in the CLDR. Please advice if it
> would be possible to submit for inclusion.
>
> Regards,
> Sebastian