Closed
Bug 1001848
Opened 10 years ago
Closed 10 years ago
(Glow2014) Country names are displayed in English for some locales
Categories
(Websites :: glow.mozilla.org, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: flod, Assigned: pmac)
References
Details
Problem is that locale for Spanish is "es", while in products Spanish is "es-ES". If I copy prod_details_json/regiones/es-ES.json as es.json, country names are correctly displayed in Spanish.
Reporter | ||
Comment 1•10 years ago
|
||
Actually the list is longer. es (product es-ES) pt-br (product pt-BR) zh-cn (product zh-CN) zh-TW (product zh-TW)
Summary: (Glow2014) Country names are displayed in English for Spanish (es) → (Glow2014) Country names are displayed in English for some locales
Comment 2•10 years ago
|
||
Those don't affect l10n but are also different from Mozilla's usual locale naming convention: en (product en-US) en-gb (product en-GB)
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Francesco Lodolo [:flod] from comment #1) > Actually the list is longer. > > es (product es-ES) > pt-br (product pt-BR) > zh-cn (product zh-CN) > zh-TW (product zh-TW) I see the 'es' issue, but those others seem to work fine for me. Is there a problem with them working on the site? I'll special-case "es" so that "es-ES" is used.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → pmac
Comment 4•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/mrburns https://github.com/mozilla/mrburns/commit/1e88b4fa165431541bc4bd3d4fa5a0581ff9d86a Fix bug 1001848: Treat 'es' locale as 'es-ES' for country names.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Paul McLanahan [:pmac] from comment #3) > I see the 'es' issue, but those others seem to work fine for me. Is there a > problem with them working on the site? https://webwewant.allizom.org/zh-TW is not available https://webwewant.allizom.org/zh-tw is available Go in "Facts & figues" and you'll see the country names in English. Now go in prod_details_json/regions, copy zh-TW.json as zh-tw.json, and you'll see the names in the correct locale.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•10 years ago
|
||
That's odd. It works for zh-tw locally for me. I'll see if I can fix this for good.
Comment 7•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/mrburns https://github.com/mozilla/mrburns/commit/1e6f8fb54a316a47fe58992de2c56b19bfe71eec Fix bug 1001848: Fix locales for countries list l10n.
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Comment 8•10 years ago
|
||
I still see some names are not translated, including British Antarctic Territory, Curaçao, Kosovo, and South Sudan. Where can I update them or just leave it alone?
Reporter | ||
Comment 9•10 years ago
|
||
Apparently those countries are not part of Product details, so I don't think we can translate them. For example there's "Sudan" but not "South Sudan", "Antarctica" but not "British Antarctic Territory". I wonder if we could hide them from the list.
Updated•10 years ago
|
Blocks: Glow:L10NTemplates
Assignee | ||
Comment 10•10 years ago
|
||
(In reply to Francesco Lodolo [:flod] from comment #9) > Apparently those countries are not part of Product details, so I don't think > we can translate them. > For example there's "Sudan" but not "South Sudan", "Antarctica" but not > "British Antarctic Territory". > > I wonder if we could hide them from the list. I can change the names. These are just country codes that show up in our data but not in prod_details. https://github.com/mozilla/mrburns/blob/master/mrburns/settings/base.py#L113-L123 If instead of new names you know to which country codes we do have I should map the others, I can just do that.
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(francesco.lodolo)
Reporter | ||
Comment 11•10 years ago
|
||
Clearing needinfo per discussion on IRC.
Flags: needinfo?(francesco.lodolo)
You need to log in
before you can comment on or make changes to this bug.
Description
•