1,035
edits
L10n:Localization Process: Difference between revisions
no edit summary
(→Getting started: undo some of the in-product webpage edits) |
No edit summary |
||
| Line 20: | Line 20: | ||
= Getting started = | = Getting started = | ||
Your first step is to try to find other community members already working on localization or willing to help out. You should find them on the [[L10n:Teams]] page, which lists the teams by [http://en.wikipedia.org/wiki/Language_code language code]. If there is not team yet, please create a wiki page in the L10n:Teams category introducing yourself, following the examples set forth in the other pages. | Your first step is to try to find other community members already working on localization or willing to help out. You should find them on the [[L10n:Teams]] page, which lists the teams by [http://en.wikipedia.org/wiki/Language_code language code]. If there is not a team yet, please create a wiki page in the L10n:Teams category introducing yourself, following the examples set forth in the other pages. | ||
The easiest way to expose your localization work to users and testers is to create, what we call a language pack, within our [https://addons.mozilla.org AMO] Add-on infrastructure. By following this route of development you get all the benefits that AMO brings: you don't have to worry about hosting costs, AMO will serve updates to your language pack to your users when they get public, you can create a nice description for your language pack, and in your language, too. Also, because we're not changing our language strings on stable releases, so with the Add-on compatibility rules, your language pack will continue to work during minor updates. [THIS SENTENCE needs work] | The easiest way to expose your localization work to users and testers is to create, what we call a language pack, within our [https://addons.mozilla.org AMO] Add-on infrastructure. By following this route of development you get all the benefits that AMO brings: you don't have to worry about hosting costs, AMO will serve updates to your language pack to your users when they get public, you can create a nice description for your language pack, and in your language, too. Also, because we're not changing our language strings on stable releases, so with the Add-on compatibility rules, your language pack will continue to work during minor updates. [THIS SENTENCE needs work] | ||