Localization (L10n) is the process of translating software user interfaces from one language to another and adapting it to suit a foreign culture. These resources are for anyone with an interest in the technical aspects involved in localization. They are for developers and all contributors.
- 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)
- Encodings for localization files
- When creating a localization for Mozilla products, it’s important to be aware of the encoding of the files that you generate.
- gettext lets you define and use singular and plural forms of a string. To take advantage of this functionality, you need to use a different keyword (i.e. different gettext function name) for string which are supposed to support plurals. For instance, in PHP the default keyword for regular messages is
_(). For messages with plural support, the default keyword is
- Found 42 pages:
- L10n Checks
- L10n Checks is a Python script and library similar to compare-locales. It allows Mozilla localizers to easily check their work.
- 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. For example, "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 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:
- Localizing with Koala
- This tutorial will guide you through making a couple of changes to Firefox's user interface using Koala, an add-on for Komodo Edit created to help localizing Mozilla.
- Localizing with Mercurial
- In Mozilla, we use the the Mercurial version control system (Hg) to manage our source code and localizations. Mercurial allows localizers to work locally (on their machines) and then
push(an Hg term) changes to a remote repository, which usually is hosted on the Mozilla servers (hg.mozilla.org). Localizing current versions of Firefox, Thunderbird and SeaMonkey includes working with Mercurial. If the documentation is incomplete or you have questions, please drop by the #l10n or #hg channels on irc.mozilla.org. The Mercurial FAQ are also worth a read, should you run into trouble.