Closed Bug 529051 Opened 15 years ago Closed 15 years ago

[tr] 3.6 whatsnew/firstrun localization

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Unassigned)

References

Details

This bug is for the localization of the new firstrun and whatsnew pages for Firefox 3.6. 

These pages are located on a separate svn branch only for 3.6 work:

https://svn.mozilla.org/projects/mozilla.com/branches/firefox3.6/ADDYOURLOCALECODEHERE

You will first need to check out your repository, example in a console for Chinese:

svn co https://svn.mozilla.org/projects/mozilla.com/branches/firefox3.6/zh-CN/ .

There are 3 pages to translate, all very short, you have a copy of these pages in your locale folder on svn, here are the paths:

/firefox/3.6/firstrun/index.html
/firefox/3.6/whatsnew/index.html
/includes/l10n/in-product-3.6.inc.php

The last file (in-product-3.6.inc.php) is used by both firstrun and whatsnew pages.

You will find attached to bug 528943 an archive of the files to translate if you do not have SVN access. If you use the archive, please attach your translations to this bug and not to bug 528943 :)

The staging site for these pages currently works for en-US so you can see what the pages will be like:

http://www-3.6.stage.mozilla.com/en-US/firefox/3.6/firstrun/
http://www-3.6.stage.mozilla.com/en-US/firefox/3.6/whatsnew/

(you need Firefox 3.6beta to display the pages correctly).


Thanks!
Seen in r57443. Please use this revision for the production site.
One missing string has been detected + some polish work. Please use r57444 for tr/includes/l10n/in-product-3.6.inc.php
pages look good, marking fixed, thanks
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
I fixed a few typos in r76197 and r76198.

Could you push these? Thanks.
Selim, I just pushed your updates to production
Component: www.mozilla.org/firefox → www.mozilla.org
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.