Closed
Bug 1438632
Opened 7 years ago
Closed 7 years ago
[kn] Wrong language names in defines.inc
Categories
(Mozilla Localizations :: kn / Kannada, defect)
Mozilla Localizations
kn / Kannada
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: grahamperrin, Assigned: flod)
Details
User Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:56.0) Gecko/20100101 Firefox/56.0.4 Waterfox/56.0.4
Build ID: 20180213113756
Steps to reproduce:
<https://github.com/MrAlex94/Waterfox/issues/440> with an extension to Waterfox, based on Firefox 56.0.2, I sought US-related language packs
Actual results:
I found langpack-kn@waterfox
Jan Beich observed,
> … Firefox 58.0.2 ships kn.xpi as … (US) Language Pack, see <https://hg.mozilla.org/l10n-central/kn/file/tip/toolkit/defines.inc>
Expected results:
Maybe (IN) in lieu of (US)?
Updated•7 years ago
|
Component: Untriaged → kn / Kannada
Product: Firefox → Mozilla Localizations
Version: 58 Branch → unspecified
Assignee | ||
Comment 1•7 years ago
|
||
Thanks for reporting. Sadly, that string is confusing, since it should not be translated.
In English is "English (US)", it should be translated as "Kannada (IN)", or "Kannada", in Kannada language.
https://pontoon.mozilla.org/kn/firefox/toolkit/defines.inc/?search=MOZ_LANG_TITLE&string=79135
So, something like "ಕನ್ನಡ" (according to Google Translate).
Note that this is just the displayed name, it doesn't have any practical effect on the localization itself.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Kannada kn locale wrongly associated with US → Wrong language names in defines.inc
Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(omshivaprakash)
Assignee | ||
Updated•7 years ago
|
Summary: Wrong language names in defines.inc → [kn] Wrong language names in defines.inc
Assignee | ||
Comment 2•7 years ago
|
||
Looks like this finally landed
https://hg.mozilla.org/l10n-central/kn/rev/e555015be148#l2.5
Assignee: nobody → francesco.lodolo
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(omshivaprakash)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•