Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
| Line 29: | Line 29: | ||
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]. | 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. | When it comes to (preview) releases, we will post more process to the [http://www.mozilla.org/community/developer-forums.html#dev-l10n Mozilla L10n newsgroup/list]. | ||
Even though parts of it are getting outdated slowly, reading 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 can probably still answer some further questions. | |||
=== Localized extensions === | === Localized extensions === | ||
edits