1457341 - [kab] Verify language and region names from CLDR

Status: RESOLVED FIXED

(Mozilla Localizations :: kab / Kabyle, defect)

Description

[Delphine Lebédel [:delphine - Use needinfo]]

Attachment: kab.txt

Translations for both language and region names are available in CLDR, but right now we ask all our localization teams to provide their own translations for them.

For reference, language names are used in preferences to set up the Accept Language setting (Language section in General), but also in the context menu for dictionaries.

In the long term, we'd like to use CLDR as a source for this data; for this reason we're investigating the differences between our localizations and CLDR, spot checking some languages.

So far we've started with a subset of languages (see Bug 1416148 for the ones we've already covered), finding that most times CLDR had the right information. As a next step, we decided to move to other languages with an high percentage of differences:
* There are 203 language names in Mozilla, 160 (78.82%) have a different translation compared to CLDR. That's over average (46%).
* There are 272 region names in Mozilla, 176 (64.71%) have a different translation compared to CLDR. That's over average (31%).

https://hg.mozilla.org/l10n-central/kab/file/default/toolkit/chrome/global/regionNames.properties
https://hg.mozilla.org/l10n-central/kab/file/default/toolkit/chrome/global/languageNames.properties

Here's the ask:
- Can you go through the list of differences, and explain the reason for so many differences?
- Would the CLDR names need to be adapted to be used in Firefox?
- Can the CLDR data be improved? 

One more note: some language and region names differ between Mozilla and CLDR. As a consequence, translation will be different. For example, "Southern Sotho" vs "Sotho, Southern", or "Caribbean Netherlands" vs "Bonaire, Sint Eustatius, and Saba".

See also bug 1434854 for an example (Italian).

Comment 1

[Francesco Lodolo [:flod]]

One thing that I missed while creating the data: some language names are basically not translated in CLDR, e.g.

ast
  CLDR: ast
  Mozilla: tasturit

The translation is missing, so they use the locale code.

Please focus on the language and region names that have an actual translation, e.g. 

es
  CLDR: taspenyulit
  Mozilla: taspanit

Comment 2

[Belkacem Mohammed]

Hi Francesco,

Validation process in CLDR is complex. The name of languages in CLDR 33 are the same as what we translated in Mozilla but they are still unconfirmed due to the validation process in CLDR (they are still unconfirmed). We still working on it (CLDR). 

We should keep Mozilla translations as the team is more important and the we will work on CLDR, it's almost the same team working on both projects. For instance, we  will keep Mozilla translations.

Comment 3

[[e-mail]]

Hi (In reply to Belkacem Mohammed from comment #2)
> Hi MUHEND,

Yes, We should keep Mozilla's translations since they are right, and work on CLDR soon, to syncronize all the translations.

Comment 4

[Francesco Lodolo [:flod]]

Considering this initiative complete.