Closed
Bug 967856
Opened 10 years ago
Closed 10 years ago
[B2G][l10n][FTE] Czech: Firefox OS Privacy Policy is not translated
Categories
(Mozilla Localizations :: cs / Czech, defect)
Tracking
(b2g-v1.2 affected, b2g-v1.3 affected)
RESOLVED
INVALID
People
(Reporter: gbennett, Assigned: JasnaPaka)
Details
(Keywords: l12y, Whiteboard: LocRun1.3)
Attachments
(1 file)
81.67 KB,
image/png
|
Details |
Description: The entire Firefox OS privacy isn't translated when the language is set to Czech. Repro Steps: 1) Updated Buri 1.3 mozRIL to BuildID: 20140203181708 2) Go to Geolocation and select "More about your privacy" 3) Select Firefox OS Actual: Privacy policy is shown in English. Expected: Privacy policy is shown in the proper language. Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20140203181708 Gaia: bb36b4164d3e51ca04b612e507e1178f80bf240d Gecko: 9731b0b7fa78 Version: 28.0 Firmware Version: v1.2-device.cfg Repro frequency: 3/3, 100% Link to failed test case: http://goo.gl/aj3ESP See attached: 2014-02-04-17-02-12.png
Comment 1•10 years ago
|
||
Invalid - it's intentional that marketplace doesn't have a translated privacy policy due to legal reasons.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Reopening as the title was incorrect.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: [B2G][l10n][FTE] Czech: Firefox Marketplace Privacy Policy is not translated → [B2G][l10n][FTE] Czech: Firefox OS Privacy Policy is not translated
Assignee | ||
Comment 3•10 years ago
|
||
Jason, the same situation for privacy policy for Firefox OS? Invalid?
Flags: needinfo?(jsmith)
Assignee | ||
Updated•10 years ago
|
Assignee: p.franc → pcvrcek
Comment 5•10 years ago
|
||
Still invalid. Privacy Policy translation is not managed by l10n teams but by Mozilla's legal team. Usually the localization in a specific locale is provided and published right before the official launch. So it's expected to be not localized at this point.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•