AMO:Localizers

Update: Home Page » Localizers' Guide

Introduction

One of the big advantages of Remora is support for localization.

Generally, localizations will only be accepted from people who are already active members of a language team which starts here.

Steps to localizing AMO in a new language

This is a comprehensive list of steps to completely localize addons.mozilla.org's interface from English into another language.

• Search Bugzilla for the words "AMO Localization (xx)" where xx is your locale code.
  • If a bug appears for your locale, then someone is already working on it. This will be a case by case basis depending on how far along the translation is, but if the bug isn't resolved, I'd suggest commenting in the bug and offering to help there.

• Assuming a bug doesn't exist, create a new bug with a Summary of "AMO Localization (xx)" (replace xx with your locale) and a description announcing your intention to localize AMO for that locale.

• Join the AMO l10n mailing list so you can get notified when strings are added or changed

• Translate the main english gettext file
  • If you're not sure what the Plural-Forms are for your language, mention this in the bug and we can help
  • Attach the completed document to your bug

• Translate the specialized pages except for privacy.thtml
  • We can't accept translations of privacy.thtml at this time
  • Attach each of the translated files separately to your bug

• Translate the strings for the flowchart
  • We'll create the image for you, just attach the translated strings to your bug

• When this is all complete, please post a comment in your bug asking for all updates to be pushed to the staging site for review.

• Once everything is setup, when you login to addons.mozilla.org, there will be a link in the left menu that says "localizer tools." It holds links to change dynamic data in the system - it's pretty intuitive, but if you'd like more instruction here, look us up in #addons on irc. You should look at this link as soon as it's available to you, because all the categories, add-on types, etc. are here and need to be translated.

An optional (but recommended) aside:

After a locale has been setup, it's possible for a localizer to add/edit translations with little to no help from the admins/developers. We're happy to assist if we can, but once a localizer learns the process, we usually just slow things down, so:

I suspect most (if not all) localizers already have SVN accounts for mozilla.com (from bug 356627). If you have an account already, and you would like to be able to manage the files in SVN yourself (this is everything that isn't dynamic data), please:

• Reopen the original bug that was filed to get you mozilla.com SVN access
• In the comments, request SVN access to (replace ___ with your locale):
  • svn+ssh://svn.mozilla.org/addons/trunk/app/site/locale/___