Closed Bug 528943 Opened 15 years ago Closed 14 years ago

[tracking] Firefox 3.6 firstrun/whatsnew localization

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Unassigned)

References

Details

Attachments

(6 files, 1 obsolete file)

This is a tracking bug for the localization of the new firstrun and whatsnew pages for Firefox 3.6. Per locale bugs will be filed for the actual translation work. Those per-locale bugs are the ones to use to attach your translated files or give the revision of your translation. 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. I am also attaching to this bug an archive of the files to translate for those that do not have SVN access. 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). I will put a notice in this bug when the staging server works for localized pages too so as that you can check how your translations fit. Thanks!
Depends on: 528917, 528265
Summary: [tracking] Fitrefox 3.6 firstrun/whatsnew localization → [tracking] Firefox 3.6 firstrun/whatsnew localization
Depends on: 528965
Depends on: 528970
Depends on: 528971
Depends on: 528972
Depends on: 528973
Depends on: 528976
Depends on: 528978
Depends on: 528979
Depends on: 528980
Depends on: 528981
Depends on: 528983
Depends on: 528984
Depends on: 528985
Depends on: 528986
Depends on: 528989
Depends on: 528991
Depends on: 528992
Depends on: 528993
Depends on: 528995
Depends on: 528996
Depends on: 528997
Depends on: 528998
Depends on: 528999
Depends on: 529000
Depends on: 529001
Depends on: 529002
Depends on: 529003
Depends on: 529004
Depends on: 529006
Depends on: 529008
Depends on: 529009
Depends on: 529010
Depends on: 529011
Depends on: 529012
Depends on: 529013
Depends on: 529014
Depends on: 529015
Depends on: 529016
Depends on: 529017
Depends on: 529018
Depends on: 529019
Depends on: 529020
Depends on: 529021
Depends on: 529022
Depends on: 529023
Depends on: 529024
Depends on: 529025
Depends on: 529026
Depends on: 529027
Depends on: 529028
Depends on: 529030
Depends on: 529031
Depends on: 529032
Depends on: 529033
Depends on: 529035
Depends on: 529036
Depends on: 529037
Depends on: 529039
Depends on: 529040
Depends on: 529042
Depends on: 529043
Depends on: 529044
Depends on: 529045
Depends on: 529046
Depends on: 529047
Depends on: 529048
Depends on: 529049
Depends on: 529050
Depends on: 529051
Depends on: 529052
Depends on: 529053
Depends on: 529059
Depends on: 529060
On the staging pages, just below the images of Personas, there's a link pointing to <http://www.getpersonas.com/en-US/getting_started>. The link text is "What are Personas?". However, I can't find that text in the files I translated. How do we translate that text?
(In reply to comment #1) > On the staging pages, just below the images of Personas, there's a link > pointing to <http://www.getpersonas.com/en-US/getting_started>. The link text > is "What are Personas?". However, I can't find that text in the files I > translated. > How do we translate that text? Hi Michael. I'd be glad to help here, but I'm not exactly sure what you're asking. What information do you need, exactly? Also, I should note that this link takes you to an en-US page, so if anyone is uncomfortable with localizing it you can leave it out (it was a late addition to the page). But, if you are comfortable with localizing it then it's a helpful thing to have on there.
Michael, that link was a late addition to the page and it leads to a section that is not going to be localized for 3.6, that's why it was not included in the files to localize.
The staging site is now functional.
Depends on: 529473
Depends on: 529509
pt-BR would love to include the orkut community in addition to Facebook; is it possible? if not, Facebook is still priority in this case...
(In reply to comment #6) > pt-BR would love to include the orkut community in addition to Facebook; is it > possible? > > if not, Facebook is still priority in this case... It's really up to you - we want this decision to be in the hands of the localizers, because you guys know the needs of your local communities far better than anyone else. That's why Sarah posted that list of alternate sites in comment #4. The only catch is that we only have room for two social networks in this layout. My assumption was that, because Orkut and Facebook have more in common with each other than they do with Twitter, most people would be choosing between Facebook and another local choice. But, like I said, ultimately it's up to you. Thanks!
hi john! actually, i was asking about orkut in addition to Facebook AND Twitter. I understand that most of localizers would prefer replace Facebook with another social network, but since there's no room for a third social network, Facebook and Twitter are still my choices... anyway, thank you for clarifying that!
Pascal, looks like there is a small problem with font. Have a look at czech (cs) translation (https://cs.www-3.6.stage.mozilla.com/cs/firefox/3.6/whatsnew/) and look at non-ascii chars like "č", "ě" or "ď".
Another problem in localized sites: the iframe loads a different page than en-US. Example: https://it.www-3.6.stage.mozilla.com/it/firefox/3.6/whatsnew/
We have finished the German (de) translation: r56345. There are two issues with the layout, though: The text on the left, describing Personas looks ugly with the line breaks. Would it be possible to change the layout, so the text fits in two lines, breaking as follows?: Daraufhalten zum Ausprobieren, anklicken zum Übernehmen Additionally, the text "Werden Sie ein Fan auf Facebook" on the right has a line break. Would it be possible to make the text fit in one line? * <https://de.www-3.6.stage.mozilla.com/de/firefox/3.6/firstrun/> * <https://de.www-3.6.stage.mozilla.com/de/firefox/3.6/whatsnew/>
(In reply to comment #11) > There are two issues with the layout, though: Hi Michael. Unfortunately I don't speak German so I can't advise you specifically, but you can definitely make whatever edits you deem necessary to make the layout work. Changing the line break on the Personas description text sounds fine, and keeping the Facebook text to a single line is important. This applies to any other localizations facing a similar issue. Thanks!
Pavel, I already filed a bug about that : bug #529509, we'll get that fixed Francesco, the bug you are seeing is on getpersonas locale detection, I also filed it this week: bug #529473 Michael, I already fixed lots of small issues via CSS yesterday, I'll keep on working on that this week and we will change the markup on a per locale basis as a last resort.
Another consideration about the en-US whatsnew page: I think the title would be better without the closing period, since the result is "You’re now running Firefox 3.6.", or even worse "You’re now running Firefox 3.6.1."
(In reply to comment #14) > Another consideration about the en-US whatsnew page: I think the title would be > better without the closing period, since the result is "You’re now running > Firefox 3.6.", or even worse "You’re now running Firefox 3.6.1." Interesting suggestion. But, with that new sentence suggestion, you have no punctuation at the end. Does that seem odd to the average end-user who may read the sentence and think of a lack of punctuation before the dangling version number? I don't really know because I can see both points. It is a title of a page. Does that allow for more flexibility with punctuation?
Pascal, is it intended that the two links to Mozilla's mission lead to two different URL's? From firstrun: /<?=$lang?>/firefox/about/ From whatsnew: /<?=$lang?>/about/whatismozilla.html
Another thing: it looks like the MetaBold font face used in these pages doesn't support even latin-based accented characters. Mozilla should look into acquiring a version with bigger character repertoire.
Rq, yes the different url are intended and we bought the larger set of fonts after I filed a bug about it.
Attached file Kurdish (ku) files (obsolete) —
Kurdish (ku) files.
Translation of a line about 'personas' in-product-3.6.inc.php has been changed. Firstly i didn't understand how personas work. But i got it now.
Attachment #414902 - Attachment is obsolete: true
Why link to Personas goes to GetPersonas.com (which is in English) instead of AMO which is translated to many languages?
Pavel, because getpersonas.com is where the Personas are and can be installed (the lightweigth themes, not the extension). We also have plans to propose getpersonas.com for localization.
Pascal, there are thousands of Personas available on amo. Check the https://addons.mozilla.org/en-US/firefox/personas/ where you can find over 36000 Personas ready for instant installation. Localizing getpersonas.com is just pointless additional pressure on the localizers.
Vlado, I didn't know about it. That's a very good point. Let's keep the getpersonas.com link for now (I can mass change it for all locales), I will meet the Personas folks next week (trip to the US) and discuss that with them face to face ! :)
Questions: 1. I noticed there are 110n mods in {$config['file_root']}/includes/headers/3.6/firstrun-l10n.inc.php. Should I submit CSS for my own locale or you would do it for us? 2. There has been some discussion on l10n-dev mailing list about "Personas" as a (do-not-translate) brand name and "parsona" as a (translatable) generic noun. So how about "Choose Your Persona" (lower caps, singular) on the title? Is it translatable? If so, how do we expose brand name if it is translated?
I noticed that the font size has increased; now some buttons have a line break. Should this reverted to a smaller font size so that there ar no line breaks?
Thomas, I'll check style for CSS for all locales when we have most of them translated.
Tim, to answer your questions: 1/ no, I will do it 2/ I looked at your pages and I think the way you did it is good
Is there a staging server available for testing Persian (fa) translation with regard to how it looks like in RTL mode?
Translation for Oriya (or).
Corrected the missing translation for Oriya (or).
Attached file Tamil (ta) Translation
Tamil (ta) Translation.
all dependencies fixed, closing the tracking bug
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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.

Attachment

General

Created:
Updated:
Size: