Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey:Localization: Difference between revisions
Jump to navigation
Jump to search
update for hg
(update for hg) |
|||
| Line 3: | Line 3: | ||
There are two ways to do SeaMonkey localization: | There are two ways to do SeaMonkey localization: | ||
*the old Mozilla suite process used for SeaMonkey 1.x | *the old Mozilla suite process used for SeaMonkey 1.x | ||
*the new | *the new source-based process for SeaMonkey 2 | ||
== The old SeaMonkey 1.x process == | == The old SeaMonkey 1.x process == | ||
| Line 15: | Line 15: | ||
If you have further questions, please ask those in [http://www.mozilla.org/community/developer-forums.html#dev-l10n mozilla.dev.l10n], which is our central hub for coordination of localization efforts at Mozilla. | If you have further questions, please ask those in [http://www.mozilla.org/community/developer-forums.html#dev-l10n mozilla.dev.l10n], which is our central hub for coordination of localization efforts at Mozilla. | ||
== The | == 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 | 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. | ||
The localization there can also use the [[L10n:Simple_locale_names|simpler locale names]] like "de", "eo", "pl", "cs", etc. | 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. | 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. | ||
| Line 31: | Line 31: | ||
[http://groups.google.com/groups?selm=Ef6dneIA776VwhLanZ2dnUVZ_sudnZ2d@mozilla.org&rnum=1 CVS-based L10n packs for venkman (JavaScript Debugger)] points out the same process for venkman. | [http://groups.google.com/groups?selm=Ef6dneIA776VwhLanZ2dnUVZ_sudnZ2d@mozilla.org&rnum=1 CVS-based L10n packs for venkman (JavaScript Debugger)] points out the same process for venkman. | ||
DOM inspector has its localizations in | 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. | 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. | ||