[B2G][2.0][l10n][Usage] Swahili: "Reset mobile & Wi-Fi data" is truncated in the "Reset" options

RESOLVED FIXED

Status

Mozilla Localizations
sw / Swahili
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: DerekH, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.0 affected)

Details

(Whiteboard: LocRun2.0)

Attachments

(1 attachment)

Created attachment 8449679 [details]
Reset mobile and Wi-Fi

Description:
When language is set to Swahili, and the user navigates through the usage app, then selects "Reset" from the Usage settings page, one of the menu option will be truncated

Prerequisites: Have  SIM in the device

Repro Steps:
1) Update a Flame to 20140702000201
2) Change language to Swahili
3) Reset or reflash the DUT
4) Open Usage App>Continue all the way through set up
5) Tap the Gear icon> Tap 'Reset'

Actual:
The menu option "Reset mobile & Wi-Fi data" is truncated

Expected:
No strings are truncated

Environmental Variables:
Device: Flame 2.0
BuildID: 20140702000201
Gaia: 3bfe47c58c959c42f5ffe0309b5380ea514ccd69
Gecko: f40e767ea283
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Notes:
Repro frequency: 3/3, 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/12835/
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

Swahili was not an available language.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)

Updated

4 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Fixed in Pootle, therefore marking as Resolved Fixed. Needs verification now
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.