[uk] change 'uk' to '@AB_CD@' in browser/firefox-l10n.js and mobile/android/mobile-l10n.js



9 years ago
3 years ago


(Reporter: Pike, Assigned: artem)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



9 years ago
Right now, 'uk' is hard-coded in the firefox-l10n.js file.

That's not a practical problem, but we've just ran into an issue where locale codes change and then things get surprising.

Mind changing that back?

Comment 1

9 years ago
Sure, will commit now. Can you share a bit of background on this?

Comment 2

9 years ago
The scottish gaelic version used the irish localization, which hard-codes ga-IE, and thus gd is running as the wrong locale.

There are some renames of locale codes ahead for locales like pa-IN, too, or more generally locales where we should use script tags in the locale code.

Nothing affecting Ukrainian, I guess. Not sure if anyone would base their localization on Ukrainian either, but it's better to have a good working template used all around.

Comment 3

4 years ago
Is it still actual?
Flags: needinfo?(l10n)

Comment 5

4 years ago
Thanks Axel!
As I understood, the string
pref("general.useragent.locale", "uk");
should be replaced with
pref("general.useragent.locale", "uk_UA");

If I'm wrong, please give me the right correction for this string.
(In reply to Artem Polivanchuk from comment #5)
> pref("general.useragent.locale", "uk_UA");

No, it actually needs to be literally "@AB_CD@"

pref("general.useragent.locale", "@AB_CD@");

And this affects also mobile for Ukranian
Summary: [uk] change 'uk' to '@AB_CD@' in browser/firefox-l10n.js → [uk] change 'uk' to '@AB_CD@' in browser/firefox-l10n.js and mobile/android/mobile-l10n.js

Comment 7

4 years ago
Thank you, Francesco!
Just pushed changes: https://hg.mozilla.org/releases/l10n/mozilla-aurora/uk/rev/f1fe8dba0c99
Please, check if everything is correct.
Looks good to me. 

BTW, is anyone still working on l10n-central for 'uk'? I tried to pull the changesets from mozilla-aurora and it merges clean but, if nobody is actually doing work there, it might make sense to push the merged state to aurora and keep l10n-central in sync from time to time.
Assignee: nobody → a.polivanchuk

Comment 9

3 years ago
So, is it already fixed?
l10n-central is not fixed yet, I think I'd need a clarification about it (e.g. if we can merge aurora into central and ignore the current content).

Comment 11

3 years ago
Created attachment 8632520 [details]
Merged to Central

Already in central.


3 years ago
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.