Closed
Bug 893410
Opened 12 years ago
Closed 11 years ago
[B2G][l10n][Browser] Hungarian: "Server not found" page is not localized in Hungarian
Categories
(Mozilla Localizations :: hu / Hungarian, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sarsenyev, Assigned: kelemeng)
References
Details
(Keywords: l12y, Whiteboard: LocRun1.2)
Attachments
(2 files)
Description:
In "Hungarian", the browser page after entering the address gives the result in English
Repro Steps:
1) Updated to Leo Build ID: 20130713070207
2) In the "Settings" change a language to "Hungarian"
3) Open the browser app
4) Tap on the URL bar and enter "usr.bin.woot"(without the quotes)
Actual Results:
The "Server not found" page is not localized.
Expected Results:
The browser will be localized in all supported languages.
Environmental Variables
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/f21152a848da
Gaia: 2e711c1fdd2441bda34703cd7d8d3c0f1cc2c396
Platform Version: 18.1
See the screenshot
Updated•12 years ago
|
Depends on: 893802
Summary: [B2G][l10n][Browser] Deutsch: "Server not found" page is not localized in Hungarian → [B2G][l10n][Browser] Hungarian: "Server not found" page is not localized in Hungarian
Updated•12 years ago
|
Assignee: timar74 → kelemeng
QA Contact: timar74 → kami911
Comment 2•11 years ago
|
||
Yeah apparently the "Server not found" page in the browser is not localized in Hungarian, whereas it is in other locales
Comment 3•11 years ago
|
||
Oh wait it looks like this depends on Bug 893802... my bad
Comment 4•11 years ago
|
||
This issue reproduces on the latest 1.2 build.
Environmental Variables:
Device: Buri v 1.2 COM RIL
BuildID: 20131022004000
Gaia: 00d5964eabf95a6a8a632420dfa36fc76dcbc9b7
Gecko: 7453a764f9a9
Version: 26.0a2
Firmware Version: 20131015
Whiteboard: LocRun1.2
Assignee | ||
Comment 5•11 years ago
|
||
As of 2.0 a localized custom message is displayed instead of the stock Gecko page.
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•