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 French and Italian, finding that most times CLDR had the right information. As a next step, we decided to move to other languages, with different scripts or higher percentage of differences: * There are 203 language names in Mozilla, 91 (44.83%) have a different translation compared to CLDR. That's slightly under average (46%). * There are 272 region names in Mozilla, 45 (16,54%) have a different translation compared to CLDR. That's below average (31%). https://hg.mozilla.org/l10n-central/bg/file/default/toolkit/chrome/global/regionNames.properties https://hg.mozilla.org/l10n-central/bg/file/default/toolkit/chrome/global/languageNames.properties Here's the ask: - Can you go through the list of differences, and explain the reason for such 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 (Italian) for an example of the discussion about differences, and links to support changes to be reported back to CLDR.
Attachment #8956847 - Attachment description: bg.txt → Differences for Bulgarian (bg)
Stoyan, did you have a chance to look at this?
See Also: → https://unicode.org/cldr/trac/ticket/11028
Yes, the repository is updated.
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Thanks Stoyan, that's great.
You need to log in before you can comment on or make changes to this bug.