The OpenOffice.org Localization Project Wiki
Localization project provides tools and creates workflows supporting localization and the internationalization of OpenOffice.org making it ready for your language.
This project relies on an effort of native-language teams, project members of OpenOffice.org Native Language Confederation project, to build a great language experience for all users worldwide, maintain translations for more than 100 languages, test and release localized OpenOffice.org installations and language packs, create localized documentation and official website, support and promote OpenOffice.org among users, partners and developers.
These wiki pages contain useful information how to to support your language in OpenOffice.org and release a localized OpenOffice.org version. Joining your Native Language project is a great opportunity to help spread our loving OpenOffice.org software and the idea of software freedom by making it accessible to more users.
When you first start at OpenOffice.org, everything is new, and the procedures may be different from other projects you've experienced. Continue reading and find out how you can contribute to your native language project or start a project to add a new language. To get in touch with the translations community please come and ask for some advice on the email@example.com mailing list (browse archive), or on the #openoffice.org IRC channel.
Comments, corrections and improvements on the wiki documents are welcome. If you wish to, you can also copy them, use them somewhere else, or anything that would be permitted by a Creative Commons Attribution License (meaning that credit is welcome).
Supporting a language
First thing that may come to your mind when thinking about supporting a language in OpenOffice.org is User Interface (UI) or Online Help (Help) translation. But actually first and more important step is to have your language recognized inside the software with correct locale data. This will allow users to set document or character language, use local number and date formats or use localized lists numbering.
On the other hand supporting a language is more than translating. You may want to provide spelling and grammar checking support, hyphenation patterns, thesaurus dictionaries and auto-correction data. Some languages require transliteration or special search capabilities, and sometimes data for automatic language recognition need to be updated.
If you want to start localizing OpenOffice.org into new language, you can propose new Native-Language Project inside Native-Language Confederation. Each Native-Language project can have an official website space at http://xx.openoffice.org where xx is your language code for information sharing on your language and dedicated mailing lists (firstname.lastname@example.org) for communication inside your local community. Native-Language project leads and co-leads have a vote in the OpenOffice.org Community Council elections for the Native Language Confederation Representative.
To get OpenOffice.org officially released in your language together with all others, you should follow the translation schedule as created and announced on the email@example.com mailing list, and test and finally approve localized builds for release.
There is a set of templates and wizards bundled with the software that can be localized. Both OpenOffice.org Templates and Extensions repository websites can be translated to your language. Many popular open-source extensions and templates published in the repositories supports and call for translations.
Some active native language projects are successful in providing translated guides and documentation for end users and developers like documentation available on this Wiki. Under Native Language Confederation umbrella they are called Level II projects as in their local activities they join global OpenOffice.org community support and marketing efforts.
Become an OpenOffice.org contributor
Add text on creating openoffice.org account and signing copyright assignment...