Closed
Bug 1032995
Opened 10 years ago
Closed 10 years ago
[B2G][2.0][l10n][Settings] Global: 'Add more keyboards' list is untranslated
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g-v1.3 affected, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)
People
(Reporter: rpribble, Unassigned)
Details
(Whiteboard: LocRun2.0)
Attachments
(2 files)
Description:
The 'Add more keyboards' list in the keyboard settings page is shown in English and remains untranslated. Languages checked include Tamil, Deutsch, Français, Español, Italiano, and Polski.
Repro Steps:
1) Update a Flame to BuildID: 20140630000201
2) Change language to Tamil (தமிழ்) or any of those listed in the description
3) Restart device
4) Settings > Keyboards > Selected keyboards > Add more keyboards
Actual:
'Add more keyboards' list is untranslated.
Expected:
No truncation occurs.
v2.0 Environmental Variables:
Device: Flame v2.0 MOZ ril
BuildID: 20140630000201
Gaia: c0c8ad187c0466285f2580531e09f8322996f561
Gecko: d4dc609bcc8a
Version: 32.0a2
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32
Keywords: localization, translate, built-in, number
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/12367/
See attached: Screenshot
-------------------------------------------------------
This issue does not occur on 1.4 Flame.
Environmental Variables:
Device: Flame 1.4
BuildID: 20140630000201
Gaia: aa896d5db1b4929f3bf31a0f4bb7de50530222a8
Gecko: 8cba60bc12ef
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Tamil was not an available language.
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Comment 1•10 years ago
|
||
This needs a regression check since this is a hard coded issue and not a localization issue. You will need to update the tracking flags after this has been checked.
Also, your comment that this does not occur on the 1.4 Flame because Tamil was not an available language does not make sense here.
Do not file bugs under the "General" component. Change this to the correct component.
This is also a "regression" so this should have been added to the keywords section.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(rpribble)
Comment 2•10 years ago
|
||
This should not block to the Meta bug either since this not a truncation issue.
No longer blocks: 1032262
Reporter | ||
Comment 3•10 years ago
|
||
Note:
-Disregard the v1.4 variables and statement in the description. The following information is correct.
-Did not add the regression keyword since it occurs on all branches.
This issue also occurs on 1.4 Flame.
Environmental Variables:
Device: Flame 1.4 MOZ ril
BuildID: 20140630000201
Gaia: aa896d5db1b4929f3bf31a0f4bb7de50530222a8
Gecko: 8cba60bc12ef
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
The keyboard selection list appears in English.
-------------------------------------------------------
This issue also occurs on the Flame v2.1 MOZ ril.
v2.1 Environmental Variables:
Device: Flame v2.1 MOZ
BuildID: 20140702040207
Gaia: 85e97290431ce6aa0a965421e84d6070cd899129
Gecko: 7075808c3306
Version: 33.0a1
Firmware Version: v122
The keyboard selection list appears in English.
-------------------------------------------------------
This issue also occurs on the Buri v2.0 MOZ ril.
v2.0 Environmental Variables:
Device: Buri v2.0 MOZ ril
BuildID: 20140626000202
Gaia: 6a1373340b40fcfe901336bc9e80676e5f2ba979
Gecko: 82ef9bf64d87
Version: 32.0a2
Firmware Version: v1.2-device.cfg
The keyboard selection list appears in English.
status-b2g-v1.4:
--- → affected
status-b2g-v2.1:
--- → affected
Component: General → Gaia::Settings
Flags: needinfo?(rpribble) → needinfo?(ktucker)
Reporter | ||
Comment 4•10 years ago
|
||
This issue also occurs on the Buri v1.3 MOZ ril.
v1.3 Environmental Variables:
Device: Buri v1.3 MOZ ril
BuildID: 20140703024002
Gaia: e08beb0297aff472b5c84437e9d7eaf8c0400a29
Gecko: cecdb4197b6e
Version: 28.0
Firmware Version: v1.2-device.cfg
The keyboard selection list appears in English.
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
status-b2g-v1.3:
--- → affected
Comment 5•10 years ago
|
||
Please provide the user agent for each branch. Also, attach a logcat even though this may not be useful.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(rpribble)
Reporter | ||
Comment 6•10 years ago
|
||
User agents:
1.3
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0
1.4
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
2.0
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
2.1
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Flags: needinfo?(rpribble)
Comment 7•10 years ago
|
||
That's not English, that's the name of the keyboard in its own language, and it sounds pretty right to me. For the same reason you don't see "Italian" but "Italiano" in Settings->Languages.
The only one that should be localizable is "Number", and we already have a string for that
http://transvision.mozfr.org/string/?entity=apps/keyboard/manifest.properties:number.name&repo=gaia
CCing Rudy, since this sounds more ::Keyboards than ::Settings too.
Comment 8•10 years ago
|
||
This is missing a needinfo to the lead to re-evaluate the QAnalyst-Triage decision.
Flags: needinfo?(rpribble)
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(rpribble) → needinfo?(jmitchell)
Comment 9•10 years ago
|
||
Not nomming based on comment 7, that everything appears correctly except the "number" string
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 10•10 years ago
|
||
Marking this as invalid, I filed a different bug for "Number" (bug 1039999).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•