Closed
Bug 815278
Opened 12 years ago
Closed 7 years ago
Localization needed for about:healthreport server side content
Categories
(Mozilla Localizations :: Other, defect)
Mozilla Localizations
Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: laura, Unassigned)
References
Details
Filed https://wiki.mozilla.org/L10n:FHRJelly with details known so far.
The content is not yet finalized, but will consist of HTML that will be served over the web and be used by Firefox to render about:healthreport.
This is a web localization bug, but the tracker is filed under Firefox:General, so I wasn't clear how to file this as per https://wiki.mozilla.org/L10n:Localizing_Projects_and_Content. Please correct as needed.
Comment 1•12 years ago
|
||
Will a new specialized website be built to host that content or will it be part of an existing site?
Reporter | ||
Comment 2•12 years ago
|
||
A new specialized site will be built.
Comment 3•12 years ago
|
||
A few more questions:
- Will this about:healthreport be an url available for desktop Firefox only or also for Firefox for Android?
- If this is going to get regular text updates, like weekly, will text updates be created the week before they are in the product or several weeks before?
- Will there be a testing server set up soon to have an idea of what it will look like?
Thanks
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #3)
> A few more questions:
>
> - Will this about:healthreport be an url available for desktop Firefox only
> or also for Firefox for Android?
I believe it is only for desktop. ccing deinspanjer for comment.
> - If this is going to get regular text updates, like weekly, will text
> updates be created the week before they are in the product or several weeks
> before?
This one is for deinspanjer or tnorris. My question: how far in advance would you like it to be done?
> - Will there be a testing server set up soon to have an idea of what it will
> look like?
I will file an infra bug soon and put the bug number in here.
Also, we think it might be easiest if we use the same l10n process as start.mozilla.org. Is that a good way to go?
Comment 5•12 years ago
|
||
In reply to Pascal Chevrel:pascalc from comment #3)
> A few more questions:
>
> - Will this about:healthreport be an url available for desktop Firefox only
> or also for Firefox for Android?
Initial release will be desktop only, but will eventually be released on Android.
> - If this is going to get regular text updates, like weekly, will text
> updates be created the week before they are in the product or several weeks
> before?
The reason for the smaller iterative updates is so we can fine-tune the actual visualizations. Changes to strings should only be happening per Fx release, and should be available several weeks before.
> - Will there be a testing server set up soon to have an idea of what it will
> look like?
Right now the majority of strings are in the product. The externally hosted iframe exists for a small set of data visualizations. For that we are still in process of finalizing the functional spec (amazing how complex a single graph can be). Once that is done we'll get the designs from UX.
Until then we won't know exactly how many strings are needed. In the first release of visualizations there will only be a single graph, so at most we'd have a dozen short strings.
Reporter | ||
Comment 6•12 years ago
|
||
We intend for this to work exactly the same as start.m.o, which means using .lang files.
Strings are supposed to be finalized today, and we should have the repo and staging environment set up shortly. jakem is point from Ops.
Depends on: 844170
Updated•12 years ago
|
Comment hidden (admin-reviewed) |
Comment 9•7 years ago
|
||
@Yuriy
This is a production Bugzilla instance. If you want to test it out, please use
https://landfill.bugzilla.org/ instead.
tracking-fennec: ? → ---
blocking-fx: ? → ---
status-firefox55:
? → ---
status-firefox56:
? → ---
status-firefox57:
? → ---
status-firefox-esr52:
? → ---
tracking-seamonkey2.48:
? → ---
tracking-seamonkey2.49esr:
? → ---
tracking-seamonkey2.50:
? → ---
tracking-seamonkey2.51:
? → ---
tracking-seamonkey2.52:
? → ---
tracking-seamonkey2.53:
? → ---
tracking-seamonkey2.54:
? → ---
Flags: sec-bounty?
Flags: in-testsuite?
Flags: in-qa-testsuite?
Flags: in-moztrap?
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•