(background: Since we moved to the rapid release cycle, we no longer display a whatsnew page when users get an automatic upgrade of Firefox, but we didn't remove this ability and sometimes we need to reactivate that page to send a specific message for a release) Firefox 13 has two new visible features for end-users, the redisigned home page and, more importantly, the new about:newtab page. We are going to warn our users about that and show them a small subtitled video to describe this feature (the video is hooked into Universal subtiles). Here is the page on the test server: http://www-dev.allizom.org/fy-NL/firefox/13.0/whatsnew/ Here is the video on Universal Subtitles: http://www.universalsubtitles.org/fr/videos/E8uQz89NVFi4/info/ There are two files to translate, one for the page itself, one for the video subtitles: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/fy-NL/whatsnew.lang?view=co http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/fy-NL/videos/video_fx13.lang?view=co (whatsnew.lang will also be reused in the future if we need to create another What's New page) Note that there are also two links pointing to documentation on http://support.mozilla.org, if you can also translate these documents that would of course be great! If you are already a Universal Subtitles user, you may want to upload the resulting .srt file yourself so as that it shows up among your video translations. You can generate a .srt file that can be uploaded through Universal Subtitles editing interface here: http://l10n.mozilla-community.org/~pascalc/langchecker/unisubs/?locale=fy-NL (just wait 15mn after committing to svn for the server to pick your updated file) Thanks!
Created attachment 639668 [details] Frisian translation Frisian translation Pascal, can you add them to the system? tanslation on universal has been submitted too. TIA Wim
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.