Localization at Mozilla

Documentation

Application Translation with Mercurial

First, get the required programs to compile Mozilla applications like Firefox and Thunderbird from Build Instructions. This is only necessary once.

Bootstrapping a new locale

(see also https://developer.mozilla.org/en/Create_a_new_localization)

Index

Found 30 pages:

L10n testing with xcode

Once you have your l10n testing environment set up in Xcode, testing your Firefox on iOS localization is a breeze.

Localization and Plurals

You're likely here because you're localizing a .properties file and it had a link to this page. This page is to help explain how to localize these strings so that the correct plural form is shown to the user. E.g., "1 page" vs "2 pages".

Localization content best practices

This document provides best practices for developers to create localizable code, and describes how to avoid some localizability (l12y) common mistakes.

Localization notes

Localizers usually work on the localizable files without the context of the source files including the localized strings; it is important to add comments to the localizable files themselves, too. These comments are generally referred to as localization notes. There is an established format for those, which is described in this document.

Localization prerequisites

To work on localization, you need a subset of the Mozilla Build Prerequisites. On Mac and Linux, you should be just fine, and on Windows, MozillaBuild should get you everything you need.

Localization quick start guide

This guide is filled with all of the basic, technical information you need to get involved in the Mozilla l10n program.

Localization sign-off reviews

This article presents an overview of why we do sign-off reviews of localizations, the details on the criteria used for the sign-off reviews, and the process for requesting a review and for following its progress.

Localization technical reviews

This guide provides details on what a localization technical review is, what criteria are used for the technical reviews, and the process for requesting one and following its progress.

Localization: Frequently asked questions

This page lists tweaks and tips that may not require a complete page on its own. For more detailed documentation about localization in general, see our Localization page.

Localizing XLIFF files for iOS

Firefox for iOS uses the XLIFF XML-based file format to hold and transfer localization data. XLIFF (eXtensible Localisation Interchange File Format) is a localization standard governed by the OASIS standards body. The goal of the standard is to have an XML-based format to use when exchanging localization data between tools without the potential of data loss or corruption. Most translation tools support the XLIFF standard, making localizing the XLIFF files for Firefox for iOS easy to do using translation tools. Editing the raw XLIFF file is also rather easy, especially if you're already familiar with XML. This tutorial will walk you through the steps you need to take to translation strings within an XLIFF file.

Localizing an extension

This article expands upon the previous samples on extension writing by adding localization support to our stock watcher extension. Performing a few simple steps makes your extension much easier to localize into various languages without having to edit the XUL or JavaScript files themselves.

Localizing extension descriptions

This article provides details on how to go about localizing the descriptions of Mozilla add-ons, as well as for other metadata about your add-on.

Localizing extension metadata on addons.mozilla.org

AMO supports localized metadata for each extension. This data describes the extension, and doesn't necessarily change with each revision (but it can). The localizable data fields of an extension are: