L10n:Browserchoice

From MozillaWiki
Jump to: navigation, search

Browserchoice is part of L10n:EU_Browser_Ballot.

This is the page users will visit after clicking on the 'Learn more' button on the ballot screen.

Basic info

Final URL
http://browserchoice.mozilla.com
Stage URL
http://browserchoice.stage.mozilla.com

The staging server is set up to auto-refresh:

  • svn up every 10 minutes
  • compile *.po to *.mo every 15 minutes.
Note: The locale detection hasn't been yet set up on the staging server. In order to preview your translations, please specify the gettext-like code of your locale, including the encoding. For example:
  1. http://browserchoice.stage.mozilla.com/?locale=pl_PL.utf8
  2. http://browserchoice.stage.mozilla.com/?locale=el_GR.utf8
  3. http://browserchoice.stage.mozilla.com/?locale=fy_NL.utf8
Tracking bug
bug eubrowserchoice-l10n

Timeline

French and Dutch locales:

  • First target date: Thursday, February 18th
  • Second target date (deadline): Monday, February 22nd

Other locales:

  • Target date: Wednesday, February 24th.

The ballot update will go live as a pilot in French and Dutch locales on Tuesday, February 23rd. For testing purposes, we would like to get French and Dutch locales by Thursday, February 18th, but if you can't make it by then, please plan to be ready on Monday, February 22nd.

All other locales will be included in the ballot update a couple of days later. Please finish your translations by Wednesday, February 24th.

Localization methods

The website uses gettext. You can either manually commit the messages.po file directly to the SVN or use Verbatim to do it for you.

SVN

 svn co https://svn.mozilla.org/projects/browserchoice/trunk/locale/ browserchoice
 cd browserchoice/${YOUR_LOCALE}/LC_MESSAGES
 # edit messages.po
 svn ci -m "A commit message"
  • Please do not commit the compiled messages.mo files to the SVN.

Verbatim

  1. Go to http://localize.mozilla.org/
  2. Log in.
  3. Go to http://localize.mozilla.org/verbatim/projects/browserchoice/
  4. Choose your locale and start translating.

At any point, you can have Verbatim commit your work to the SVN by pressing the Commit to VCS button on the Edit page (e.g. for Polish this is http://localize.mozilla.org/verbatim/pl/browserchoice/LC_MESSAGES/edit.html)

How to add your locale to Verbatim's project page

If your locale is not listed on http://localize.mozilla.org/verbatim/projects/browserchoice/, please follow the following steps:

  1. Go to http://localize.mozilla.org/
  2. Log in using your LDAP credentials. This will automatically create a new user account for you.
  3. Send your LDAP e-mail address to stas mozilla com in an e-mail like this:
 Subject: Access to Verbatim ${locale} for ${your ldap email}
 Body: <empty>

Staś will add proper permissions for your username.

Guidelines

When localizing browserchoice.mozilla.com page please be mindful of using a language which is in line with European advertising laws.

Essentially, if a claim can be measured as to whether we achieve it or not, then we must be able to prove that it's true absolutely. Even if there is one exception for one second, that can create problems.

Best practice: don't make claims that can be measured and are absolute. It's better to make general statements.

Examples:

Good
We care about your privacy
Protecting your privacy is a priority at Mozilla
Bad
Your privacy won't be compromised
We take every step to ensure your privacy
We have the best privacy on the web

Also, be careful about using comparative statements (or don't use them at all if in doubt). For example in the sentence: "With excellent security, advanced features and amazing customization options, Firefox is the best browser around — and it's free!" please don't use any comparative statements to describe the qualities of Firefox, such as "superior security".


To do

  • change the getpersonas link to the personas section on AMO for locales where l10n is more complete on AMO than on getpersonas.com (the link to getpersonas.com should stay for Polish, Greek, Czech and Spanish)
  • add the locale detection on /
    • but not on /xx/
  • make sure /xx and /xx/ both work
  • the personas image in the "customization" section (sethb)