[B2G][2.0][l10n][Settings] Tamil: "Cellular & Data" header displays truncated

RESOLVED FIXED

Status

Mozilla Localizations
ta / Tamil
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: Jordan de Geus(JordanD), Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.0 affected)

Details

(Whiteboard: LocRun2.0)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8451737 [details]
Cellular&Data.png

Description:
When users are in Tamil language, the "Cellular & Data" header within the Settings app displays truncated.

Setup 
Settings > Language> ta - Tamil 

Repro Steps:
1) Update a Flame device to BuildID: 20140702000201
2) Select Settings> Cellular & Data> Sim 1
3) Observe the header "Cellular & Data" headers display truncated

Actual:
"Cellular & Data" header displays truncated
Expected:
Header displays correctly without truncation.

Environmental Variables:
Device: Flame 2.0
BuildID: 20140707000200
Gaia: ef67af27dff3130d41a9139d6ae7ed640c34d922
Gecko: f53099796238
Version: 32.0a2
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.

Repro frequency: 3/3
Link to failed test case: Found this issue during exploratory testing of suite: Loc 2.0 - Tamil - Settings
See attached: Screenshots - Cellular&Data.png
(Reporter)

Comment 1

4 years ago
This issue does not occur on Flame 1.4 as the Tamil language was not available in 1.4.

Environmental Variables:
Device: Flame 1.4
Build ID: 20140702063007
Gaia: e8599c2b346addf3bf857310502e5b542ae7d0b2
Gecko: 5ff8eb391b65
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
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+]
Changed the strings in Pootle. Kindly change the status to "resolved fixed".

Updated

4 years ago
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.