Difference between revisions of "Pootle User Guide/Release Localized Build"

From Apache OpenOffice Wiki
Jump to: navigation, search
m
 
(6 intermediate revisions by 3 users not shown)
Line 21: Line 21:
 
* there is a small team (even just two members) to maintain the translation and ensure QA.
 
* there is a small team (even just two members) to maintain the translation and ensure QA.
 
   
 
   
When you are ready, write an issue in [https://issues.apache.org/ooo/enter_bug.cgi Bugzilla] in the product ''Native-Language''. Also write an issue, if you later on make changes to the translation and want them to be integrated into the next release.  
+
When you are ready, write an issue in [https://bz.apache.org/ooo/enter_bug.cgi Bugzilla] in the product ''Native-Language''. Also write an issue, if you later on make changes to the translation and want them to be integrated into the next release.
  
Once your issue if files, there are some additional steps that are needed to integrate Pootle translations into OpenOffice. These are typically done by a developer who can commit changes to the source tree and include:
+
Once your issue is filed, there are some additional steps that are needed to integrate Pootle translations into OpenOffice. These are typically done by a developer who can commit changes to the source tree and include:
* conversion of Pootle files for a language to OpenOffice SDF format (see reference at [http://translate.sourceforge.net/wiki/toolkit/oo2po http://translate.sourceforge.net/wiki/toolkit/oo2po])
+
* conversion of Pootle files for a language to OpenOffice SDF format (see reference at [http://translate.sourceforge.net/wiki/toolkit/oo2po http://translate.sourceforge.net/wiki/toolkit/oo2po])
* for new language translations -- updating the extensions.lst file in the source tree
+
  
{{Documentation/Note|If you edit strings in Pootle you need to explicitly ask on the mailing list, for them to be integrated into OpenOffice. Integration is not automatic.}}
+
These are basically database files that will reside in /extras/l10n/source under the ISO code for the language.
  
{{Documentation/HelpNeeded|Please add information how to verify the technical correctness of the translation.}}
+
* Some (new) languages might also provide dictionaries as extensions. In this case, the the extensions.lst file in the source tree under /main will need to be updated.
 +
 
 +
{{Note|If you edit strings in Pootle you need to explicitly ask on the mailing list, for them to be integrated into OpenOffice. Integration is not automatic.}}
 +
 
 +
{{HelpNeeded|EN|Please add information how to verify the technical correctness of the translation.}}
  
  

Latest revision as of 21:46, 17 February 2019

[[{{{PrevPage}}}|< Previous Page

]]

[[{{{NextPage}}}|Next Page
>]]




We have agreed to release a localized version of Apache OpenOffice, if the UI is 100% translated.

And for long-term maintainability we also recommend that:

  • the UI is translated to 100% and
  • the help is translated to 100% too and
  • there is a small team (even just two members) to maintain the translation and ensure QA.

When you are ready, write an issue in Bugzilla in the product Native-Language. Also write an issue, if you later on make changes to the translation and want them to be integrated into the next release.

Once your issue is filed, there are some additional steps that are needed to integrate Pootle translations into OpenOffice. These are typically done by a developer who can commit changes to the source tree and include:

These are basically database files that will reside in /extras/l10n/source under the ISO code for the language.

  • Some (new) languages might also provide dictionaries as extensions. In this case, the the extensions.lst file in the source tree under /main will need to be updated.
Documentation note.png If you edit strings in Pootle you need to explicitly ask on the mailing list, for them to be integrated into OpenOffice. Integration is not automatic.


Documentation needshelp.png This article needs help


Please add information how to verify the technical correctness of the translation.

Personal tools