L10n:Localization Process: Difference between revisions

Jump to navigation Jump to search
no edit summary
(end user focus now, some structure shifts still. WIP)
No edit summary
Line 1: Line 1:
{{draft}}
{{draft}}


Mozilla's [[L10n:Home_Page|L10n]] objective is offer as many users as possible a great user experience. That includes offering them the Mozilla applications in their language. The user experience follows the route
Mozilla's [[L10n:Home_Page|L10n]] objective is to offer to as many users as possible the Mozilla applications in their language with a great user experience. This user experience is:
* Finding Firefox on the web
* Finding Firefox on the web
* Installing Firefox
* Installing Firefox
Line 8: Line 8:
* Upgrading Firefox to a new major version
* Upgrading Firefox to a new major version


Now, this is obviously not the route the localizer experience follows, which is closer to
Because you, what we call a Localizer, are here, we believe you're looking for way to contribute to Mozilla applications in your language and find out what it takes -- you've started at the right place. This is a brief overview of the typical process involved in translating Mozilla applications:
* Wanting to contribute to Firefox in your language
* Localizing (translating and customizing) the application
* Finding out what it takes -- you're at the right place here
* Getting your localization to testers
* Localizing the application
* Localizing installation and migration
* Get your localization to testers
* Translating web pages linked from the application
* Localize installation and migration
* Translating Mozilla websites
* Translate web pages linked from the application
* Translate Mozilla websites


The following pages should show how those two experiences get along. You might also be interesting in localizing [http://wiki.mozilla.org/Update:Localizers AMO] or [http://developer.mozilla.org/en/docs/MDC:Localization_Projects developer documentation].
The links below explain how to achieve the L10n objectives by getting more involved.  


We're always looking for feedback to make this page better, so if you have something to say good or bad please post to the [http://www.mozilla.org/community/developer-forums.html#dev-l10n forum] or [mailto:mic@mozilla.com mail us].
You can also follow these two links in the case you are interested in localizing [http://wiki.mozilla.org/Update:Localizers AMO] or [http://developer.mozilla.org/en/docs/MDC:Localization_Projects developer documentation].
 
We are always looking for feedback to improve this page, if you have something to say good or bad please post to the [http://www.mozilla.org/community/developer-forums.html#dev-l10n forum] or [mailto:mic@mozilla.com mail us].


= Volunteer =
= Volunteer =
Volunteers wanting to contribute to a Mozilla application in their language should first try to find other community members already working on the 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 the 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.


The most lightweight way to expose your localization work to users and testers is to create an Add-on to hold your localization, a so-called language pack. Language packs can be uploaded to [https://addons.mozilla.org AMO], and get all the benefits that AMO brings from that. 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, in your language, too. 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.
The most lightweight way to expose your localization work to users and testers is to create an Add-on to hold your localization, a so-called language pack. Language packs can be uploaded to [https://addons.mozilla.org AMO], and get all the benefits that AMO brings from that. 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, in your language, too. 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.
1,035

edits

Navigation menu