Closed
Bug 854651
Opened 12 years ago
Closed 12 years ago
[es-CL] Translate .lang file for Firefox Health Report (about:healthreport)
Categories
(Mozilla Localizations :: es-CL / Spanish (Chile), defect)
Mozilla Localizations
es-CL / Spanish (Chile)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pascalc, Assigned: ravmn)
References
Details
We have the opportunity to release a new feature in Firefox, a self-auditing system giving advanced users useful information and tips about the performance of their browser. These users can also share this data with Mozilla so as to help improve Firefox performance. This new feature takes the form of a new in-product page accessible at about:healthreport
The product part of it are a few strings in the Firefox source code, the server-side part is a lang file to translate the UI, explain what the collected values are and give performance tips.
The repository for your locale is:
https://svn.mozilla.org/projects/l10n-misc/trunk/firefoxhealthreport/locale/es-CL/
The specific file to translate is:
https://svn.mozilla.org/projects/l10n-misc/trunk/firefoxhealthreport/locale/es-CL/fhr.lang
There is a staging server being set up there:
http://fhr-dev.allizom.org/es-CL/
(Note at the time of filing this bug, the staging server is not autoupdating code and translations yet and is in heavy works since localizers are working in parallel to the webdev team creating this mini-site).
We might release this feature for the next Aurora but that's totally unsure, given that this is server side, we should be able to update the server after we have released the next Firefox Aurora.
Thanks
Reporter | ||
Comment 1•12 years ago
|
||
Richard, could you update your translation ASAP? You can use both es-AR and es-ES as basis as they have finished. We release that as part of the beta tomorrow and it would be good to have the feature fully translated. Thanks
Assignee: nobody → ravmn
Reporter | ||
Comment 2•12 years ago
|
||
Fixed and live, thanks Richard!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•