Personal tools

SeaMonkey:Localization

From MozillaWiki

Jump to: navigation, search

This page describes the process of creating a SeaMonkey localization. If you want to use a localized SeaMonkey version, see our download page.

The source-based process for SeaMonkey 2

Starting with SeaMonkey 2 (and its pre-releases), we are using the same 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 following documents are good starting points for information:

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 "sea21x" tree of the Mozilla L10n dashboard and localized nightly builds as well as language packs will be created and uploaded to latest-comm-2.0-l10n ("sea22x" and latest-comm-central-trunk-l10n for in-development versions).

When it comes to (preview) releases, we will post more process to the Mozilla L10n newsgroup/list.

Even though parts of it are getting outdated slowly, reading the 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

The extensions that SeaMonkey 2 includes by default can also be localized, but there are different ways to achieve that for different extensions:

If you also want to get a localized ChatZilla in your builds, your language can be added to the supported list for that extension, as pointed out in the CVS-based ChatZilla L10n packs message on mozilla.dev.l10n.

CVS-based L10n packs for venkman (JavaScript Debugger) points out the same process for venkman.

DOM inspector has its localizations in its main Mercurial repository, you need to file a bug against DOM inspector for your locale to be added as well as for every needed update of it, always with a patch attached.

The "reporter" tool for reporting problems with websites is treated like an integrated part of SeaMonkey itself, even though its source and localization is in the extensions/ directory.

And finally, the "SeaMonkey Debug and QA UI" extension does not support localization at all, as it is not even included in release builds of SeaMonkey, it's supposed to be used for testing purposes only. Please just ignore this extension when localizing SeaMonkey.