NLC:New Translators Start here
Working together with OpenOffice.org L10n Team
OpenOffice.org L10n provides localized builds for many languages. Joining your native language project is a great opportunity to help making OpenOffice.org reach more users. Browse the languages list and get in touch with project leads.
For translation teams, with every new milestone (version of OpenOffice.org code) we provide source messages from both UI and Help to be translated.
From translation teams, we need a translation file, a SDF/GSI file containing all the English strings translated into your language (or at least 80% UI translated).
Translation teams have the possibility to maintain a localized web site at http://xx.openoffice.org (xx being a language code) if they become a native language project in the Native Language Confederation, translate user documentation published on the wiki, upload localized templates and localize OpenOffice.org templates and extensions repositories web sites. It is possible to prepare and publish locale data, spellcheck and thesaurus dictionaries, hyphenation patterns and autocorrect data as well as advanced grammar checking support.
Click here to view general information on translating OpenOffice.org using either Pootle or using Gettext PO and managing translations outside Pootle.
Starting a new localization project
Testing localized builds
I need help
OpenOffice.org is a large and complex project, so it is particularly difficult for a newcomer. Don't feel discouraged if you become confused or can't get an overview of the project.
In any case, we are all here to help each other. Please ask on the firstname.lastname@example.org mailing list if you have any problems. We will work things out together.
Good luck with your localization. :)