Closed Bug 522973 (fennec10-l10n-web) Opened 11 years ago Closed 9 years ago

Fennec Web localization, tracking bug for release

Categories

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

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Unassigned)

References

Details

This bug tracks the localization of Firefox mobile pages for all locales being released with the first release of Firefox mobile for the general audience.

Separate per locale bugs will be filed as dependencies of this bug.

Instructions on what pages are to be localized will be given in this bug.
Here is the list of pages ready to be translated on your SVN repository:

http://svn.mozilla.org/projects/mozilla.com/trunk/en-GB/mobile/
http://svn.mozilla.org/projects/mozilla.com/trunk/en-GB/m/

ab-CD/mobile/
ab-CD/mobile/sms-thanks.html
ab-CD/mobile/features/
ab-CD/mobile/sync/
ab-CD/mobile/developers/
ab-CD/mobile/faq/
ab-CD/mobile/platforms/
ab-CD/mobile/customize/

ab-CD/m/
ab-CD/m/requirements.html
ab-CD/features.html
ab-CD/faq.html
ab-CD/unsupported.html



Note that there are 5 UI strings added to your main.lang file too.

A few additional notes:

The /mobile/ pages are normal pages for people surfing mozilla.com and wanting to get information about fennec.

The /m/ are simplified pages (both content and design) for mobile devices where they can download Firefox (download logic will be added later).

The main /mobile/ page has a functionality to send an SMS message and a country selection list, this list is already translated (taken from the Firefox source code).

Currently the message sent by SMS is not final hence the text received in English, I will inform in this bug when this text is ready to be translated.

Screnshots in the pages are not final.

The FAQ and Features pages are the long ones, the others are pretty short.

The privacy page remains in English (legal document)
Depends on: 522993
Depends on: 522995
Depends on: 522996
Depends on: 522997
Depends on: 522998
Depends on: 522999
Depends on: 523000
Depends on: 523001
Depends on: 523003
Depends on: 523004
Depends on: 523005
Depends on: 523006
Depends on: 523007
Depends on: 523008
Depends on: 523009
Depends on: 523011
Depends on: 523012
Depends on: 523013
Depends on: 523014
Depends on: 523015
Depends on: 523016
Depends on: 523017
Depends on: 523018
Depends on: 523019
Depends on: 523020
Depends on: 523021
Depends on: 523022
Depends on: 523023
Depends on: 523024
Depends on: 523025
Depends on: 523026
Depends on: 523027
Depends on: 523029
Depends on: 523030
Depends on: 517152
Maybe it's just my first impression, but there's a bit of inconsistency: "mobile", "mobile phone" and "mobile device" are used as synonyms but they're not (N810 is a mobile device but it's certainly not a mobile phone).

Minor note: the same button is referred as "Tools button" (mobile/customize/index.html) and "the settings button" (mobile/sms-thanks.html). As far as I understand there are no labels or tooltips, so the second form is probably better.
Two other questions:
* is it ok to speak about "Fennec" instead of "Firefox" in mobile/platforms/index.html? It's about the desktop version, so maybe it's wanted
* typo in mobile/developers/index.html "best practies for running" -> practices (thanks to prometeo for finding it)
Alias: fennec10-l10n-web
(In reply to comment #2)
> Maybe it's just my first impression, but there's a bit of inconsistency:
> "mobile", "mobile phone" and "mobile device" are used as synonyms but they're
> not (N810 is a mobile device but it's certainly not a mobile phone).

We should assume that Firefox is being marketed for mobile devices, and specifically mobile phones.  Most development is being optimized for Nokia's N900, which is a mobile phone.  Although the N810 is a supported as a mobile device, you will see that most development resources and public messaging is pointed at the N900 right now.  I hope that helps explain at least a bit.

> Minor note: the same button is referred as "Tools button"
> (mobile/customize/index.html) and "the settings button"
> (mobile/sms-thanks.html). As far as I understand there are no labels or
> tooltips, so the second form is probably better.

Probably a good assumption.  Thanks for point this out.

(In reply to comment #3)
> Two other questions:
> * is it ok to speak about "Fennec" instead of "Firefox" in
> mobile/platforms/index.html? It's about the desktop version, so maybe it's
> wanted

No.  This is Firefox.  Fennec should be considered a code name, like Shiretoko or Namoroka.  The branding and messaging going forward will be Firefox for mobile devices.  

> * typo in mobile/developers/index.html "best practies for running" -> practices
> (thanks to prometeo for finding it)

Nice catch.  I will alert the marketing team.
Hi Seth, thanks for the tips.

We've almost finished our localization and I'm going to check the whole translation, so I could find some other issues.

For example: "Sync in, sync, and away you go." (mobile/sync/index.html)
I'm quite sure that the first "Sync in" should be "Sign in".
Another small error in mobile/faq/index.html

<a href="../">Develop for Mobile</a> should point to "../developers" (q27)
I would like to point out an factual error:

in mobile/index.html

$chooseYourCountry  = "Choose your country";

should be "Choose your country or region" or simply "Choose your location" since certain people don't regard, unfortunately, Taiwan, as a country. By choosing the right word we can save a lot of time fighting with these people and leave our position with some ambiguity.

Even if we drop the whole Taiwan issue, in the list there are still territories like American Samoa which is definitely not a country.
Thanks for all the feedback guys, I am working on integrating all of it.
Feedback integrated in r53780
/platforms/index.xhtml

There are links to Fennec builds for Windows, Linux and Mac but version is hardcoded in these links. I think you know it. Just want to be sure.
Yes, I know about it, I don't know yet what the final links will be, I will update the links on the pages when I know what the urls will be, thanks :)
Not really an l10n issue, but: the country list in "Choose your location" drop-down is currently sorted by region code, but it should be sorted by region name.
>Not really an l10n issue, but: the country list in "Choose your location" drop-down is currently sorted by region code, but it should be sorted by regionname.

Good catch, I will fix that :)
At line 53, ./m/faq.html
"Or, simply go to [mozilla.com/m] with your ..."
should link to "./" instead if "./m/".
Is there a deadline for this?
Any clue on when Mobile will be released?
> Is there a deadline for this?
> Any clue on when Mobile will be released?

Not sure about the deadline since there are so many dependencies on shipping a new product, personnally I am targetting mid November as a likely shipping date for web localization, I will ask Caitlin later today when she gets connected to give us the current shipping estimated date.
not exactly about this bug, but no changes on products (mozilla.com/products) page? it refers to Fennec as a pre-release version
>not exactly about this bug, but no changes on products (mozilla.com/products)
page? it refers to Fennec as a pre-release version

no
Found a CSS bug:

https://www-trunk.stage.mozilla.com/zh-TW/mobile/
On this page, "Standard text rates apply" is being text-wrapped.

Solution would be as simple as add "white-space: nowrap" at line 96 of 
/style/tignish/mobile-later.css
One more thing: is it possible to pre-select few locations in the location menu?
People couldn't find "Taiwan" by pressing T on the keyboard... Lists in Chinese doesn't work that way.

A better UI would be putting locale-specific locations at the top, e.g. Taiwan, Hong Kong, Macau, Singapore ...
For those looking for recommendations on how to prioritize your work flow for this large amount of web l10n, you can consider the order listed below.  Please remember that we still want all pages localized.  /mobile and /m pages are equally important, so I would work on both lists simultaneously if that makes sense.

For the ~/mobile/... pages

1. index-later
2. sms-thanks.html
3. /mobile (Coming Soon page)
4. /platforms
5. /developers
6. /customize
7. /synchronize (I would rank sych as #4 but I understand that sense Weave won't be localized yet, we're waiting).
8. /FAQ (long)
9. /Features (long)

For the ~/m/...
1. /m
2. https://www-trunk.stage.mozilla.com/en-US/m/1.0/firstrun/ (this page has been updated in the product, but copy is same).
3. /platforms
4. /features
5. /FAQ
One more addition for everyone to absorb. The page ~/mobile/index-later.html is listed in comment #21 as the first page to localize for the desktop version of our mobile browser pages.  That page will be added to the l10n repositories this weekend.  

The page ~/mobile/index.html is presently listed in your repositories.  That takes much less priority and can be item #10 in ~/mobile/.. list above.
ADDENDUM to comments #21 and 22.  The page I listed in comment #21 as "index-later" is currently in your repository as "index.html".  For reference, see this page.

http://svn.mozilla.org/projects/mozilla.com/trunk/en-GB/mobile/

Today, the mobile team asked if this page could get localized as well:

https://www-trunk.stage.mozilla.com/en-US/mobile/index

We will post that page with the proper name soon.   Once your repo is updated with the new page to localize, we will comment here to let you know.

My apologies for the confusion and please stay tuned.
Many localizers have asked if they need to localize all the mobile pages if the N900 device is not being sold in the country where their language is primarily spoken.  To help you prioritize your work, I gathered a list from Caitlin (Mozilla Mobile marketing) and the Nokia team for where the N900 will be sold.  The countries include  

* Finland - [fi]
* France - [fr]
* Germany - [de]
* Italy - [it]
* Netherlands - [nl]
* Poland - [pl]
* Spain - [es-ES]
* Sweden - [sv-SE]
* United Kingdom - [en-GB]
* USA - [en-US]

If you are localizing mobile Firefox and the country where your language is primarily spoke is *not* listed, you do not have to meet the *web l10n* deadline.  However, it would be wise to work on it since this will be the primary way that users who are interested in mobile Firefox in your language can find out about the product.  This is meant to help those asking about the work flow.
The right spelling for HTML5 is "HTML5", not "HTML 5": see http://blog.whatwg.org/spelling-html5
I've a question about the following paragraph in the mobile/faq/index.html file:
"Firefox has implemented the first public draft of the <a
href="http://www.w3.org/TR/2008/WD-geolocation-API-20081222/">Geolocation
specification from the W3C</a>. An overview on how to develop
Location-Aware websites here."

What is the last sentence for? Is anything missing here? It makes no sense for me.
> What is the last sentence for? Is anything missing here? It makes no sense for
me.

Not really clear indeed, I will ping Caitlin today about it.

For the space between HTML and 5, I will update the pages tonight.
talked to Caitlin, here should be a link but it was forgotten in the en-US document, I am going to update files on svn and will warn here when done for people to svn up.
pages are updated for all locales, please svn up
Updating the Basque localization, I noticed that there are some non-english strings in some pages of the SVN repository. For example here:
http://svn.mozilla.org/projects/mozilla.com/trunk/en-GB/m/requirements.html

I wonder if this is correct.
assar, thanks for founding that, it looks like a localizer sent his translation to the wrong locale folder.
It seems that some of the content is duplicated on both /mobile/ and /m/. Can you please tell us which content is duplicated in order to keep us from translating the same text twice?
(In reply to comment #32)
> It seems that some of the content is duplicated on both /mobile/ and /m/. Can
> you please tell us which content is duplicated in order to keep us from
> translating the same text twice?

"m" is a subset of "mobile", my personal suggestion (having already finished my localization) is to translate "mobile" first and then reuse translated strings for "m". 

But pay attention because some strings are slightly different, so you can't always copy&paste the whole strings, and URLs in links change.
as indicated by flod, the content is similar but target a different audience and different devices (mobile/ for full browsers, m/ for devices with limited browsers) so the writing style is different.
in /m/faq.html:

  <h3>How do I download Firefox to my phone?</h3>

  <p>Visit the <a href="../mobile/">Mozilla.com Mobile homepage</a> to send a text message containing a link to download Firefoxto your phone. Or, simply go to <a href="./m/">mozilla.com/m</a> with your current mobile browser and download Firefox directly to your phone.</p>


The second link is broken. Should be "../m/", or simply "./"
Also, Here's what /mobile/faq/index.html says:
    <dt id="q17">How can I share my Firefox bookmarks, history, tabs and more between my PC and my mobile?</dt>
    <dd>The Weave add-on brings your Firefox experience to your mobile phone. First, create a Weave account on your PC. Then go to Firefox on your mobile and search for and install the Weave add-on. When you enter you Weave account info and sync, your Firefox preferences, history and more will be shared between your PC and your mobile. To learn more, visit the Synchronize page.</dd>

and here's the same question and anser in /m/faq.html:

  <h3>How can I share my Firefox bookmarks, history, tabs and more between my PC and my mobile?</h3>

  <p>The Weave add-on brings your Firefox experience to your mobile phone. First, create a Weave account on your PC. Then go to Firefox on your mobile and select the pre-installed Weave add-on. When you enter your Weave account info and sync, your Firefox preferences, history and more will be shared between your PC and your mobile.</p>


I'm quite puzzled now: so is Weave preinstalled or not? The answers are quite different, and not just in length, but in meaning too.
#35 is fixed in r55819 for all locales

regarding #36, I checked with people from mobile and it is a mistake in the /m/ version (= it was supposed to be pre-installed but this integration will not be ready for 1.0 in the end).

I have updated the /m/faq.html copy in r55821 for all untranslated copies and I will warn localizers that already translated the wrong text individually as well, thanks for finding this error Rimas.
Depends on: 527718
Depends on: 527931
Message to localizers:

The Weave add-on has a new name, it is now called Weave Sync

I have updated the whole repository for that, so please update your local copy to include this change.

If you had translated the pages locally and not sent the current state of your translation to the SVN repository, please make sure that you change all ocurrences of Weave by Weave Sync in your translation.

Thanks
Be aware that there is one file that has only been updated in en-GB version, this one:
http://svn.mozilla.org/projects/mozilla.com/trunk/en-GB/mobile/sync/index.html
thanks for noticing assar, the Sync page is now also updated for all locales.
Should we translate the release notes? I think the release notes page contains essential information for users. But till now it's not possible to translate it.

We, the German translators, think that the privacy police also should be translated. Maybe this could be done by chambers for at lest the bigger languages (de, fr, ...). People have the right to read and _understand_ the privacy issues.
Thomas, I'll see tomorrow if I have time to prepare release notes for you and other interested teams, I am not sure they are final yet though.
(In reply to comment #43)
> There is broken link in
> http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/pl/mobile/sync/index.html?revision=58602&view=markup#l46
> Should be https://addons.mozilla.org/firefox/addon/10868 instead
> https://addons.mozilla.orgfirefox/addon/10868
> Looks like all locales are affected.

r59253

a little sed magic fixed this across all locales on trunk
all dependencies fixed, closing tracking bug
Status: NEW → RESOLVED
Closed: 9 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.