Confirmed users, Bureaucrats and Sysops emeriti
2,976
edits
L10n:Starting a localization: Difference between revisions
L10n:Starting a localization (view source)
Revision as of 16:46, 3 September 2007
, 3 September 2007typo, rogly to roughly
m (typo, rogly to roughly) |
|||
| Line 18: | Line 18: | ||
To make your work available for users to download and test, create a language pack which can be hosted on [https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:37 AMO]. AMO offers many advantages for both you and your testers and users, from download capacity to automatic updates of your Add-on. | To make your work available for users to download and test, create a language pack which can be hosted on [https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:37 AMO]. AMO offers many advantages for both you and your testers and users, from download capacity to automatic updates of your Add-on. | ||
Starting from scratch on a new localization depends a good deal on whether you use a [[L10n:Tools|tool]], and if so, which. On MDC, we documented [[mdc:Creating en-X-dude]], which works with the Mozilla build system and an UTF-8-capable editor. You won't need a compiler, though, no worries. The steps | Starting from scratch on a new localization depends a good deal on whether you use a [[L10n:Tools|tool]], and if so, which. On MDC, we documented [[mdc:Creating en-X-dude]], which works with the Mozilla build system and an UTF-8-capable editor. You won't need a compiler, though, no worries. The steps roughly include | ||
* Check out the [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_%28CVS%29 en-US tree]. | * Check out the [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_%28CVS%29 en-US tree]. | ||
* Once you've created your working clone, edit the resulting tree to translate the strings (perhaps with [[L10n:Tools| tools]]) | * Once you've created your working clone, edit the resulting tree to translate the strings (perhaps with [[L10n:Tools| tools]]) | ||