Closed
Bug 1033072
Opened 10 years ago
Closed 10 years ago
[B2G][2.0][l10n][Contacts] Swahili: Header for Microsoft account sign in page is not localized
Categories
(Mozilla Localizations :: sw / Swahili, defect)
Tracking
(b2g-v2.0 affected)
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
People
(Reporter: jdegeus, Unassigned)
References
Details
(Whiteboard: LocRun2.0)
Attachments
(1 file)
(deleted),
image/png
|
Details |
Description: When users are attempting to sign into their Microsoft/Outlook account to import contacts, users will see the header is not localized for Swahili Setup Settings > Language> Swahili - Kiswahili Repro Steps: 1) Update a flame device to BuildID: 20140630000201 2) Contacts > Gear(upper right corner)> Import Contacts> Outlook 3) Observe header is not being localized Actual: Header for Outlook/Microsoft account sign in is not localized for Swahili Expected: Outlook/Microsoft/Hotmail account sign in header is localized for Swahili Environmental Variables: Device: flame 2.0 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. Repro frequency: 3/3 Link to failed test case: https://moztrap.mozilla.org/manage/case/12795/ See attached: Screenshot - Swahili_Hotmail.png
Reporter | ||
Comment 1•10 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 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
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Comment 2•10 years ago
|
||
We should not be writing up untranslated issues unless it is a hard coded issue.
Status: NEW → RESOLVED
Closed: 10 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•