SeaMonkey:Localization: Difference between revisions

Jump to navigation Jump to search
(update for hg)
Line 17: Line 17:
== The source-based process for SeaMonkey 2 ==
== The source-based process for SeaMonkey 2 ==


Starting with SeaMonkey 2 (and its pre-releases), we are using the same [[L10n:Localization_Process|Localization_Process]] as Firefox, Thunderbird and Sunbird. This allows us to have all localization files in central repositories on hg.mozilla.org, share the translation for the common Mozilla core with the other mentioned applications, and build official release builds as well as nightly builds directly from the repository.
Starting with SeaMonkey 2 (and its pre-releases), we are using the same [[L10n:Localization_Process|Localization_Process]] as Firefox 3.1, Thunderbird 2 and Sunbird 1.0. This allows us to have all localization files in central repositories on hg.mozilla.org, share the translation for the common Mozilla core with the other mentioned applications, and build official release builds as well as nightly builds directly from the repository.
The localization there can also use the [[L10n:Simple_locale_names|simpler locale names]] like "de", "eo", "pl", "cs", etc.
 
This is all in all a big process change, but we now follow roughly the same guidelines as Firefox, laid out e.g. in the [http://developer.mozilla.org/en/docs/Create_a_new_localization create a new localization] page - just replace "browser" with "suite" in the Firefox localization documents and this is how it works for SeaMonkey.
The following documents are good starting points for information:
 
* [http://developer.mozilla.org/en/docs/Create_a_new_localization Create a new localization]
* [[L10n:Starting_a_localization|Starting_a_localization]]
* [http://developer.mozilla.org/En/L10n_on_Mercurial L10n on Mercurial]
 
Once your localization gets complete (check that with compare-locales), please file a bug for adding your locale to all-locales for SeaMonkey (in "SeaMonkey > Build Config") and assign it to "kairo@" so we can add you there and repackaging of nightlies will be done.
 
Once added to all-locales, your localization will appear in the "sea2x" tree of [http://l10n.mozillamessaging.com/dashboard/ the Mozilla Messaging L10n dashboard] and localized nightly builds as well as language packs will be created and uploaded to [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-l10n/ latest-comm-central-l10n].
 
When it comes to (preview) releases, we will post more process to the Mozilla L10n newsgroup/list.


You also should read the [http://home.kairo.at/blog/2007-11/source_l10n_available_for_seamonkey_trun blog post on SeaMonkey localization] written by Robert Kaiser from the SeaMonkey Council when this process was first introduced to SeaMonkey development.
You also should read the [http://home.kairo.at/blog/2007-11/source_l10n_available_for_seamonkey_trun blog post on SeaMonkey localization] written by Robert Kaiser from the SeaMonkey Council when this process was first introduced to SeaMonkey development.
Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083

edits

Navigation menu