Confirmed users, Bureaucrats and Sysops emeriti
2,976
edits
L10n:Localization Process: Difference between revisions
Jump to navigation
Jump to search
→Getting started: undo some of the in-product webpage edits
(we're much closer to translation than to localization of bookmarks) |
(→Getting started: undo some of the in-product webpage edits) |
||
| Line 24: | Line 24: | ||
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] | ||
The negative side of using AMO is that your users won't get a localized install experience of Firefox, including the profile migration dialogs. | The negative side of using AMO is that your users won't get a localized install experience of Firefox, including the profile migration dialogs. The in-product webpages will come up in one of the official languages of mozilla.com, bookmarks and search engines will be taken from the build that your users installed originally. If your users decide to upgrade to the next major version, your language packs will stop working, and get disabled like other incompatible Add-ons, until you uploaded a compatible version on AMO again. We are working on [link to any blog posts? or maybe status pages with notes about this] improving this process specifically for Language Packs to achieve our objective of a good user experience overall. If you're working on a dialect or a minority language, the disadvantages of language packs are not that bad [WHY?], but for languages spoken by people without a second language supported by the Mozilla community (thus far), getting Firefox out there requires more work. | ||
There is a detailed description of the [[L10n:Localization_Process_Start]] with links to further documentation and tools in hopes you are still willing to jump into the work of localizing :-). | There is a detailed description of the [[L10n:Localization_Process_Start]] with links to further documentation and tools in hopes you are still willing to jump into the work of localizing :-). | ||
= Official Release = | = Official Release = | ||