Difference between revisions of "NLC:New Translators Start here"
Goranrakic (Talk | contribs) |
m (→Working together with {{AOo}} L10n Team) |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Warn|This page belongs to OpenOffice.org version 3 and earlier. Current new translators start on https://openoffice.apache.org/translate.html}} | |
| − | + | == Working together with {{AOo}} L10n Team == | |
| − | + | ||
| − | + | ||
| + | {{AOo}} L10n provides localized builds for many [[Languages|languages]]. Joining your native language project is a great opportunity to help making OpenOffice reach more users. Browse the [[Languages|languages list]] and get in touch with project leads. | ||
| − | + | To get in touch with the general {{AOo}} translation community please come and say hello on the mailto:l10n@openoffice.apache.org mailing list. | |
| − | |||
| + | '''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 <tt>SDF/GSI</tt> 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 website at http://xx.openoffice.org (xx being a language code) if they become a native language project in the [[NLC|Native Language Confederation]], translate user documentation published on the wiki, upload localized templates and localize OpenOffice.org templates and extensions repositories websites. 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. | ||
== Translating OpenOffice.org == | == Translating OpenOffice.org == | ||
| − | Click here to view [[Translation:General_Information|general | + | Click here to view [[Translation:General_Information|general information on translating]] OpenOffice.org using either Pootle or using Gettext PO and managing translations outside Pootle. |
| Line 32: | Line 33: | ||
== I need help == | == I need help == | ||
| − | OpenOffice.org is large and complex project, so it is particularly difficult for a newcomer. | + | 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 [mailto: | + | In any case, we are all here to help each other. Please ask on the [mailto:l10n@openoffice.apache.org l10n@openoffice.apache.org] mailing list if you have any problems. We will work things out together. |
Good luck with your localization. :) | Good luck with your localization. :) | ||
[[Category:Localization|!]] | [[Category:Localization|!]] | ||
Latest revision as of 10:01, 31 August 2022
 |
This page belongs to OpenOffice.org version 3 and earlier. Current new translators start on https://openoffice.apache.org/translate.html |
Contents
Working together with Apache OpenOffice L10n Team
Apache OpenOffice L10n provides localized builds for many languages. Joining your native language project is a great opportunity to help making OpenOffice reach more users. Browse the languages list and get in touch with project leads.
To get in touch with the general Apache OpenOffice translation community please come and say hello on the mailto:l10n@openoffice.apache.org mailing list.
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 website 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 websites. 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.
Translating OpenOffice.org
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
First thing is to prepare new language or locale support and submit it for integration.
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 l10n@openoffice.apache.org mailing list if you have any problems. We will work things out together.
Good luck with your localization. :)
