If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[B2G] [l10n] [Nederlands] First page of the User Guide is mostly in English

NEW
Unassigned

Status

Firefox OS
Gaia::System
4 years ago
4 years ago

People

(Reporter: CKreinbring, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g18 affected)

Details

(Whiteboard: LocRun1)

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
Created attachment 759978 [details]
Screenshot of opening User Guide page

Description:
A user with their device language set to Nederlands will see the most of the titles on the starting page of the User Guide in English.

Repro Steps:
1) Updated to Unagi Build ID: 20130605070207
2) Select Instellingen, then Hulp.
3) Select Gebruikershandleiding when wait for the browser page to load.
4) Observe the text on the page that loads.

Actual:
Most of the subject titles are in English.

Expected:
All of the text on the page is in the Nederlands language.

Environmental Variables
Occurs on Unagi 1.1 commercial RIL
Build ID: 20130605070207
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/09dc1ae3b1b5
Gaia: 92a6e36957145cdb2ac8867e5cdba8ecf12308fc
Platform Version: 18.0

Notes:
Repro frequency: 100%
Test Suite Name: Settings - Help
UCID: set-091
Link to failed test case: https://moztrap.mozilla.org/manage/cases/?filter-id=3329
Q Analysts Team Priority: Pri 3
See attached screenshot
Those pages are from SUMO, not really a Gaia problem.
https://support.mozilla.org/nl/products/firefox-os
(Reporter)

Comment 2

4 years ago
Created attachment 778716 [details]
New Screenshot of opening User Guide page

The page has changed, but it still repros on Leo 1.1 commercial RIL.  A new screenshot has been attached.

Build ID: 20130719070225
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/6b6e80e9aaf0
Gaia: ce5a75acd4ad6cd0d53dad77c058a0f1002f98b1
Platform Version: 18.1
RIL Version: 01.01.00.019.164

Comment 3

4 years ago
This should have been fixed now ever since those pages have been localized.
You need to log in before you can comment on or make changes to this bug.