L10n:Starting a localization: Difference between revisions

Line 1: Line 1:
=START=
=START=
We believe our common (Mozilla [[L10n:Home_Page|L10n]] team and Localizers) objective is to get communities formed and launch new languages/locales. We all start working towards this when we receive the message from you (the Localizer) that you would like to localize one of our products. This document outlines what you should expect next. This page should take about 5 minutes to review. Having said that, there are links here to larger pages, so you might want to set aside a few hours if you're serious and ready to get into what's involved in starting a Localization project.
This document outlines what you should expect in order to start building a new language.  
*  Join an existing team or start a new one (if there isn't one already working on your language)
* Register, so people know you are working on it and can contact you
* Check out the en-US tree
* Clone it
* Edit the resulting tree to translate all the strings (perhaps with tools)
* Run some tool which bundles up the result into a language pack
* Ship it to some friends to test it
* Check in the result, and iterate.  


As described in the previous [[L10n:Localization_Process|page]], you can start by building a lanugage pack and work towards becoming an official build. There are known issues with language packs between releases we are working to fix [[https://bugzilla.mozilla.org/show_bug.cgi?id=334136|bug 334136]]  
As described in the previous [[L10n:Localization_Process|page]], you can start by building a lanugage pack and work towards becoming an official build. There are known issues with language packs between releases we are working to fix [[https://bugzilla.mozilla.org/show_bug.cgi?id=334136|bug 334136]]  
1,035

edits