[B2G][2.0][l10n][Settings] Tamil: "Sign in or Create an Account" button string is truncated in Find My Device

RESOLVED FIXED

Status

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

People

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

Tracking

(Blocks: 1 bug)

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 8450651 [details]
Screenshot.png

Description:
When users are in Tamil language, the button string "Sign in or Create an Account" displays truncated within Find My Device.

Setup 
Settings > Language> ta - Tamil 

Repro Steps:
1) Update a Flame device to BuildID: 20140702000201
2) Select Settings> Find My Device
3) Observe the button string "Sign in or Create an Account" 

Actual:
Button string "Sign in or Create an Account" is truncated in Find My Device
Expected:
Button string is not truncated

Environmental Variables:
Device: Flame 2.0
BuildID: 20140702000201
Gaia: 3bfe47c58c959c42f5ffe0309b5380ea514ccd69
Gecko: f40e767ea283
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: https://moztrap.mozilla.org/manage/case/13716/ - This fails Step 2
See attached: Screenshots - Screenshot.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.