[B2G][2.0][l10n][Find My Device] Bulgarian: "Enable Find my Device" string is truncated

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: smiko, Assigned: ogi)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.0 affected)

Details

(Whiteboard: LocRun2.0-2)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8467200 [details]
2014-08-04-11-02-39.png

Description:
The string "Enable find my device" is truncated in the Find my Device section of the Settings application.

Repro Steps:
1) Update a Flame to 20140804000204
2) Open Settings and set the language to Bulgarian
3) Navigate to Settings > Find my device

Actual:
The string "Enable Find my Device" is truncated

Expected:
No strings are truncated

Environmental Variables:
Device: Flame 2.0 319mb
Build ID: 20140804000204
Gaia: 9e5907995c9327f14cb5d182cee5ff16b1743ed4
Gecko: 3f7db58a354c
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Keywords: Bulgarian, Find My Device

Notes:
1) The title on this page is truncated as well (see bug 1048364)

Repro frequency: 100%
See attached: (screenshot)
(Reporter)

Comment 1

4 years ago
This issue does not occur in 1.4.

Find My Device does not exist in 1.4 

Environmental Variables:
Device: Flame 1.4 319mb
Build ID: 20140804063202
Gaia: 9377274b17200a60cebcd2427d489a7756c4cc72
Gecko: 93e736da9863
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Blocks: 1032262
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0: --- → affected
Flags: needinfo?(ktucker)
Whiteboard: LocRun2.0-2
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)

Updated

4 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
(Assignee)

Comment 2

4 years ago
https://hg.mozilla.org/releases/gaia-l10n/v2_0/bg/rev/cd12187babdb (along with bug 1048364)
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.