Use Common Locale Data Repository (CLDR) for locale names

NEW
Unassigned

Status

Mozilla Developer Network
Localization
3 months ago
3 months ago

People

(Reporter: jwhitlock, Unassigned)

Tracking

({in-triage})

Details

(Whiteboard: [specification][type:change])

(Reporter)

Description

3 months ago
What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
In bug 859499, we added language names to the translatable strings, so that Mozilla localization teams could localize the languages.

Instead, we should use the Unicode Consortium's Common Locale Data Repository (CLDR) [1], as included in Babel [2]


[1] http://unicode.org/cldr/
[2] http://babel.pocoo.org/en/latest/locale.html

What problems would this solve?
===============================
Active localization teams have translated the locale names, but inactive teams have not. Keeping these as localizable strings in Pontoon adds to the translation burden for new and existing locales. The Unicode CLDR should be a better maintained source for these strings.



Who would use this?
===================
Localizers, Non-English MDN users, MDN staff

What would users see?
=====================
Localizers would have 50+ less strings to translate. MDN users would see locale names in the desired languages. The instructions for MDN staff to add a locale [3] would get easier.

[3] https://kuma.readthedocs.io/en/latest/localization.html#add-a-new-locale-to-pontoon

What would users do? What would happen as a result?
===================================================
Localizers would focus on MDN-specific strings. MDN users would more easily switch to their target locales, even if it was new and not widely supported yet.

Is there anything else we should know?
======================================
Babel includes a copy of the CLDR data, so there is no network request to download it.  We already use Babel as a Kuma dependency.
Keywords: in-triage
You need to log in before you can comment on or make changes to this bug.