L10n:Starting a localization

START

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)
  • Check out these sources to determine whether your language is already started or not.
  • Also check our list of bugs filed in case there's already been interest in the language you want to build.
• Register, so people know you are working on it and can contact you
  • What we mean by register is:...
  • You should also create a wiki page that identifies you and what you're working on so people can find you.
• Check out the en-US tree, as you will be working first to build a language pack, we suggest you start at these Creating en-X-dude pages and focus on creating an installable language pack xpi.
  • If you haven't already you should also get onto the IRC Channel, #l10n. You will be able to get real-time help from other Localizers and members of the L10n-driver team. In addition, you should have already created for yourself a bugzilla account as the majority of our work is started and tracked to completion in this way. You can also post questions or offer suggestion to either L10n on Google forums or post an email. And, there is more helpful documentation on the Mozilla Development Center.
• Once you've created your working clone, edit the resulting tree to translate all the strings (perhaps with tools)
• Run some tool which bundles up the result into a language pack
• Shipping it to some friends to test it and then checking in the results, and iterating.
  • Finalizing: this is where the BIGGEST amount of your work will happen to get your build to "official" status. There are many code strings to change so read the documentation we provided above carefully and use the resources we offer extensively to get you through it successfully!

The critical elements of this stage are to ensure your build has been reviewed by the community (particularly those interested in your language) and is being used on AMO and updated regularly by you. It's important to collect input from any and all sources about your language pack as this is the first time that people will be using it on a day-to-day basis and giving you feedback about the quality of your work. It is these same users who will then download and promote your new language.

Something to think about all throughout your work is expanding the people around you who can help you with the language you're working on. This is a good thing and will be useful for you for testing, celebratory events (i.e, launch parties), and possibly web pages or other areas you might need or want help with. We want to help with this and are working on programs to do so. (You can read more about this on Seth's blog about our global program).

To move forward from this stage you would request a review to make your build "official".

There are known issues with language packs between releases we are working to fix [334136].

Useful tips. I'd really like to improve on this section, so if you feel you have some useful tips please feel free to edit this section with additional helpful sources of information.

Now on to the Building and Preparation stage of the L10n:Localization_Process overview.