I’d like to announce our plans for the localization of Lightning for 1.0 and beyond. I’ve done my best to make the process as little work for the localizers as possible, so please excuse if the naming and repos don’t currently match whats usual for Firefox and Thunderbird. I promise this will change for the following releases though.
First of all, lets focus on Lightning 1.0 which is due November 8th. As with the last two releases, we will be using l10n-miramar. The main reason for this is that we’ve taken great care to not change any strings for 1.0b7 and the upcoming 1.0 release. Note however, the tree to compare with is not comm-miramar, but rather comm-beta. This may be a bit confusing, but be assured this name clash will go away after the release. Currently, 38 locales are green and only 11 are red. I would love to see a few more locales going green for 1.0. How about it? According to the current state of the l10n dashboard, here’s a list of the missing locales. Maybe you can help out? If so, please click on the links below and contact the team leaders there:
If you already localize for any of these locales and you know everything is translated, please request sign-off again to make sure it shows up as green on the dashboard.
The following information is not relevant for Lightning 1.0. We haven’t agreed on version numbers, but we do have l10n trees and will be leaving l10n-miramar after the release. Given Lightning has a binary component and needs to re-release every time that Thunderbird does, it makes sense for us get aboard the release train too. You can see the l10n trees here:
- cal_beta (with l10n mozilla-beta): currently not relevant, but will be after the merge on November 8th
- cal_aurora (with l10n mozilla-aurora): compares with the current comm-aurora, or the release due December 20th
- cal_central (with l10n central): compares with the current comm-central, or the release due January 31st
If you have any questions, please do let me know via comment or email.