This page is aimed at current and future localizers of Thunderbird, Mozilla Messaging's e-mail and usenet client. It covers many aspects a localizer of Thunderbird should be aware of like necessary tools, how to get information about localization-relevant events and various other items of interest.
Creating a new localization (Mercurial) - This article describes how you can create a new localization for Thunderbird.
There are 3 active repositories for Thunderbird development. Thunderbird development work is merged from one branch to the next every six weeks.
- comm-central - also known as Trunk or "Daily".
- This is where regular Thunderbird development takes place. Strings change at any time.
- Only a few locales are expected to translate on this branch.
- comm-aurora - also known as "Earlybird"
- This is where development for a particular release starts to be stabilised.
- No new features are allowed, and strings are frozen.
- Locales should do as much of their work as possible on this branch and achieve sign-off.
- Work done here will automatically be merged to beta and release every 6 weeks.
- comm-beta - "Beta" channel
- This is where we preview Thunderbird development to a large amount of users.
- Final stabilisations are performed.
- Little or no l10n work is done here.
Most locales will being working on comm-aurora. This repository/branch is stable with respect to strings for each six week period. Completing work here means it is ready for the first beta, and you won't need to work on beta branch. Your work will also automatically be carried forward.
There are not significant restrictions on what locales can change. However, we need to work together on providing search engines for Thunderbird users to use to get the right balance of search engines and the correct options set. For further information see this page.
A localization will added to the l10n dashboard on request when it has reached a high-level of completion (> 80%) as shown by the compare-locales output. To request the addition of your locale to the dashboard, file a bug in the Thunderbird product/Build Config component.
Localizers of Thunderbird should read the localization newsgroups (mozilla.dev.l10n.announce mozilla.dev.l10n) to stay informed of Thunderbird-specific and general l10n-related items of interest to them. They are further encouraged to read the Thunderbird development newsgroup (mozilla.dev.apps.thunderbird) to stay informed of recent Thunderbird-related developments.
These newsgroups can also be accessed via the firstname.lastname@example.org, email@example.com (localization mailinglist) or firstname.lastname@example.org (Thunderbird development mailinglist) mailinglists, which mirror the newsgroups mentioned above. You can subscribe to or unsubscribe from these mailinglists via the web interface at lists.mozilla.org.
Localizers should watch the email@example.com mail address (or its alias :tb-l10n) to stay current on bugs that might affect Thunderbird localizers. This can be done by adding this mail address to the "User Watching" section of your Email preferences in bugzilla.
Locale tiers reflect locales that we need to have in a good state for release. There are 10 locales in tier 1, which are the most important for Thunderbird, because of their number of Thunderbird users or potential for growth.
These locales are being treated as first-class citizens, as important as en-US, which is to say that any Tier 1 locale that does not meet the requirements may block a final release of Thunderbird.
The following are P1 (priority 1) locales in order of priority:
* de - German * fr - French * ja, ja-JP-mac - Japanese * en-GB - British English * es-ES - Spanish (European continent) * it - Italian * pl - Polish * ru - Russian * nl - Dutch * pt-BR - Brazilian Portuguese
All other supported locales are in the tier 2 category.