[lo] Verify language and region names from CLDR

REOPENED
Unassigned

Status

enhancement
REOPENED
a year ago
a year ago

People

(Reporter: delphine, Unassigned)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

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 197 language names in Mozilla, 193 (97.97%) have a different translation compared to CLDR. That's over average (46%).
* There are 272 region names in Mozilla, 154 (56,62%) have a different translation compared to CLDR. That's over average (31%).

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

As a reference we used "lo" in CLDR.
https://github.com/unicode-cldr/cldr-localenames-modern/tree/master/main

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).
Flags: needinfo?(kavhanxay)
Adding another localizer from the "lo" community so this might possibly get some traction.
Please do let me know if anything is unclear! (also seems like there are only 2 people in the Lao l10n community have bugzilla accounts? I'll try to reach out by email, there should definitely be more)
thanks!
Flags: needinfo?(saleumsack16)

Comment 3

a year ago
Hello, Sorry for the late answer. Does the bugzilla and mozilla has to login in as seperate acc? or can use the same acc? I'll tell my local team for more information 

Thanks
Flags: needinfo?(saleumsack16)
(In reply to saleumsack16 from comment #3)
> Hello, Sorry for the late answer. Does the bugzilla and mozilla has to login
> in as seperate acc? or can use the same acc? I'll tell my local team for
> more information 

Not sure I understand the question, in particular "Mozilla login"? If you're talking about Firefox Account, it cannot be used to log in to Bugzilla. You need to create an account on Bugzilla, and use the same email used in other services. 
https://bugzilla.mozilla.org/createaccount.cgi
(In reply to saleumsack16 from comment #3)
> Hello, Sorry for the late answer. Does the bugzilla and mozilla has to login
> in as seperate acc? or can use the same acc? I'll tell my local team for
> more information 
> 
> Thanks

I suggest you to tell other member to create their own account. So other member can follow "lo" component and see the activity for your locale on bugzilla as Delphine mentioned in the email.
Wanted to check-in to know if there was anything unclear about this request, and if you needed me to clarify a part of the ask?

What we're really interested in knowing is: 
- 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? 

Please let me know if you have any question! thanks
it's different because the first one is country name and the second one is language name.

Generally you can use this in Firefox.
Status: NEW → RESOLVED
Last Resolved: a year ago
Flags: needinfo?(kavhanxay)
Resolution: --- → FIXED
(In reply to Saikeo Kavhanxay from comment #7)
> it's different because the first one is country name and the second one is
> language name.

Can you explain with an example?

Also, the plan is to use CLDR in the future, replacing existing localization. Would that work? If not, why?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
For example:
In regionNames.properties, la = Laos.
In languageNames.properties, lo = Lao language.

In regionNames.properties, ru = Russia.
languageNames.properties, ru = Russian language.


Yes, you can use CLDR in the future, replacing existing localization.
Status: REOPENED → RESOLVED
Last Resolved: a year agoa year ago
Resolution: --- → FIXED
@Saikeo
Please, let's keep this but open until we reach an agreement.

Looking at the attachment.

In CLDR Russian it's ລັດເຊຍ, while in Mozilla is ພາສາລັດເຊຍ. Why the difference? Which one is correct?

Or regions: Mexico (MX) is ເມັກຊິໂກ in CLDR, ແມັກຊີໂກ in Mozilla. Same questions.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Russian = ພາສາລັດເຊຍ not ລັດເຊຍ

"Mexico (MX) is ເມັກຊິໂກ in CLDR, ແມັກຊີໂກ in Mozilla" I think some localizer wrong translate it. Mexico (MX) is ເມັກຊິໂກ, ແມັກຊີໂກ is incorrect in spelling.
(In reply to Saikeo Kavhanxay from comment #11)
> Russian = ພາສາລັດເຊຍ not ລັດເຊຍ

Why not? Is ລັດເຊຍ the country, not the language?

That's the kind of analysis that we're asking to do on the attachment
https://bugzilla.mozilla.org/attachment.cgi?id=8968644

In it you can find CLDR and Mozilla translation. If you need to match a language code to the language name, you can use
https://searchfox.org/mozilla-central/source/toolkit/locales/en-US/chrome/global/languageNames.properties

For regions
https://searchfox.org/mozilla-central/source/toolkit/locales/en-US/chrome/global/regionNames.properties
Because ລັດເຊຍ is country's name not language's name.
You need to log in before you can comment on or make changes to this bug.