Closed
Bug 546191
Opened 14 years ago
Closed 14 years ago
[tracking] Firefox 3.0 to 3.6 Major Update page localization
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pascalc, Unassigned)
References
Details
Attachments
(1 file)
968 bytes,
text/plain
|
Details |
This bug tracks the localization of the Major Update box that will be proposed to Firefox 3.0 users to incitate them to upgrade to 3.6 This page will be displayed into a XUL dialog box when the Major Update will be offered. Here is the page to be translated in your SVN repository: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-GB/firefox/3.6/details/from-3_0.html?revision=62239&content-type=text%2Fplain&view=co (A copy of this file is in each locale directory that had a Firefox 3.0.x release.) You can see your translation online on the staging site: http://www-trunk.stage.mozilla.com/en-GB/firefox/3.6/details/from-3_0.html Separate, per locale, bugs will be filed as dependencies of this bug. Please commit directly on SVN and inform in your depending bug when the pages are ready, you can also attach the translated page to your bug and I will commit it for you. Reminder, the URL of the repository where your files are is: https://svn.mozilla.org/projects/mozilla.com/trunk/PUTYOURLOCALECODEHERE Thanks!
Comment 1•14 years ago
|
||
Kurdish (ku) translation is here. I wonder why it is writing "Beta langiage" for Kurdish here? http://www.mozilla.com/ku/ I think there is no reason for that. (Maybe it is not right place to ask that, but i didnt know where i can ask about that.)
Reporter | ||
Updated•14 years ago
|
Attachment #427077 -
Attachment mime type: text/html → text/plain
Reporter | ||
Comment 2•14 years ago
|
||
committed in r62321, thanks. Amed, Kurdish was released as beta locale because it was ready very late in the release process for 3.6, it will probably be de-betaed in a 3.6.x release.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 3•14 years ago
|
||
Pascal, thanx for answering. I will wait for 3.6.x :)
Reporter | ||
Comment 4•14 years ago
|
||
marked fixed by mistake, too many tabs open :)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 5•14 years ago
|
||
These need to be in place before we can have FF3.0.18 users do manual CheckForUpdates to upgrade to FF3.6.0. Hence marking as blocking. Note: we are planning to ship FF3.0.18 tomorrow, and typically support users doing manual CheckForUpdates. Will these pages be ready by tomorrow?
Blocks: 543853
Reporter | ||
Comment 6•14 years ago
|
||
John, it's not going to be ready for tomorrow, we are at 41 locales tonight out of 61 and several others will be done tomorrow so we will probably be around 50, which is already great in so little time since the final English text was chosen last week. Creating a page for so many locales requires usually 3 weeks at least. We can put a copy of 3.6/details/index.html for locales that we won't have tomorrow since it's already translated though.
Comment 7•14 years ago
|
||
I have questions about the wording: Shouldn't we use the word "upgrade" instead of "update"?
Reporter | ||
Comment 8•14 years ago
|
||
Tim, I think we are using the word update instead of upgrade because the latter can seem a bit scary for people that are afraid of installing software (hence the focus in the sub text about settings not being lost) and we are actually trying to convince the last 3.0.x users to move to a supported branch so as to stop supporting the old 3.0.x branch. If you think that "upgrade" is a better word for your locale, feel free to use it though.
Comment 9•14 years ago
|
||
(In reply to comment #6) > John, it's not going to be ready for tomorrow, we are at 41 locales tonight out > of 61 and several others will be done tomorrow so we will probably be around > 50, which is already great in so little time since the final English text was > chosen last week. Creating a page for so many locales requires usually 3 weeks > at least. !00% agreed. No question its cool that soooo many locales are ready so quickly. > We can put a copy of 3.6/details/index.html for locales that we won't > have tomorrow since it's already translated though. This actually addresses what I was concerned about. I was worried we might have to hold the MU offer part of tomorrow's 3.0.18 release. However, if we are able to use the pre-existing billboards for the locales that have not refreshed, then we're not risking blocking tomorrow's release so I'm happy - its all good. Thanks Pascal.
Comment 10•14 years ago
|
||
commited to SVN at rev:62801
Reporter | ||
Comment 11•14 years ago
|
||
Closing as we will not have the last locale (mn) and this page will soon be replaced by another one
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Component: www.mozilla.org/firefox → www.mozilla.org
Assignee | ||
Updated•12 years ago
|
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.
Description
•