Translation for 2.3

From Apache OpenOffice Wiki
Jump to: navigation, search

For the translation update of the OpenOffice.org 2.3 version a number of native language Communities has volunteered to contribute to the translation work for which Sun usually provides translation:

The Communities who have adhered to this initiative are:

  • Dutch Community
  • French Community
  • Germanophone Community
  • Italian Community
  • Spanish Community
  • Brazilian Community
  • Swedish Community
  • Russian Community
  • Chinese Community - new on board!

Schedule

Due to the large translaiton volume that needs to be updated, for this release there will be 2 translation hand-offs:

  • 1st translation hand-off - COMPLETED

Translation start date: June 7th
Translation delivery date: July 5th at noon CET

Estimated volume: approx. 25,000 words

  • 2nd translation hand-off

Translation start date: July 12th
Translation delivery date: July 26th at noon CET

Estimated volume: approx: 7,000 words


Release Map with translation deadlines specific for the 2.3 release can be found at: http://wiki.services.openoffice.org/wiki/OOoRelease23

General Process

The files to be translated by the Community members will be in SDF file format and will be delivered as zip file attached to an l10n issue. The SDF file format - which can be read and edited with a simple text editor - can be converted into .po files. Once the Communities have finalized the translation of the files, they will backconvert the po files into sdf file format, run the gsicheck on the sdf file, make coccections in the file in case or errors and return the issue to the submitter attaching the translated files. The Sun Language Leads will then perform linguistic review on the translated files and will provide their feedback to the n-l communities via QA matrix attached to the issue. No changes will be carried out in the files translated by the community members unless there is a common agreement on the changes. Changes in the translated files which are not exlicitely declared as show stopper in Issue Tracker will be integrated into the next release. All Communities receiving a QA matrix will need to carry out the changes in the previously translated files and return to Sun within 2 weeks from the QA matrix delivery date.

Process Step by Step

  • Sun creates issues and attaches .sdf files to translate (volume to be decided by each Community based on their availability and resources)
  • Issues will be assigned to the translation Community leads
  • Community converts into po files (if any problem with that we will take over conversion)
  • Community translates the files using a translation .po editor
  • Community back converts the .po files into .sdf
  • Community runs gsicheck on sdf and delivers back to Sun
  • Sun will import the translated files into 2.3
  • Language lead will carry our linguistic review
  • Community will implement linguistic review results into translated files and deliver updated files 2 weeks after QA matrix delivery.

Issues containing .sdf files

Tips and Tools

Team:

build a team of translators and 1-2 reviewers to work on the project. I recommend to keep the number of the reviewers to 1-2 people, since the more translators and reviewers working on the project, the less you can ensure quality and consistency. For all the above language there is a Sun Language Lead who may consulted in case of language related questions.

Glossary:

SunGloss (https://g11nportal.sun.com/sungloss) is the repository of the latest terminology used in the StarOffice/OpenOffice.org product. You can request access to consult the tool. We recommend to use SunGloss instead of a spreadsheet because it shows all entries (including deleted entries that were used but not anymore). In this way it's possible for all to look at the evolution of a translation, and discuss about it when it's needed, especially during the review process.

Tools:

The .sdf file can be converted to .po files using the oo2po tool and converted back to .sdf format using the po2oo tool from the Translate Toolkit package: http://translate.sourceforge.net/

Documentation with examples for conversion and backconversion can be found at: http://translate.sourceforge.net/wiki/toolkit/oo2po

gsicheck to make sure the translated .sdf files are not corrupted can be found at: http://ooo.services.openoffice.org/gsicheck/

The most used translation editors supporting the .po file format are:

poEdit runs both on Windows and Linux. Kbabel runs on Linux only but it seems to be more professional. Please add further information on these and other tools that may help other translators to perform their job.

Roles and Responsibilities

Language N-L Lead
main contact(s)
Language Lead Central Engineer(s) Project Lead Other
Brazilian Portuguese Olivier Halllot
Claudio Filho
Augusta Marques Da Silva Petr Dudacek Rafaella Braconi  
Dutch Arthur Buijs Natalie Koning Petr Dudacek Rafaella Braconi  
French Sophie Gautier Elsa Blume Petr Dudacek Rafaella Braconi  
German Jacqueline Rahemipour
Marko Moeller
Berit Bonde Petr Dudacek Rafaella Braconi  
Italian Andrea Pescetti
Alessandro Cattelan
Monica Badia Petr Dudacek Rafaella Braconi  
Russian Rail Aliev TBD Petr Dudacek Rafaella Braconi  
Spanish Santiago Bosio
Alexandro Colorado
Aridane Vilardane-Viegra Petr Dudacek Rafaella Braconi  
Swedish Lars D. Noodén
Erik Magnus Johansson
Sofia Nilsson Petr Dudacek Rafaella Braconi  
Simplified Chinese Lin Cheng
Joy Zhang Aijin Kim Rafaella Braconi  


Files for Translation

Q & A

This session will be filled in with Q & As which will be raised and answered during the translation initiative

Q: Which is the total wordcount estimated for the update 2.3 release?
A: The estimated total wordcount is 25,000 words. GUI approx. 3000 words, Online Help approx. 22,000 words.

Q: Is there any tool which can convert automatically a two-language text glossary into a PO file, for example the glossary extracted from the SunGloss?
A: Open your text file in OOo Calc as a CSV file and choose "tab" as the delimiter. Save it as a normal CSV file (comma seperated) and then you can convert it to PO using csv2po from the translate toolkit. Here is the documentation for that: http://translate.sourceforge.net/wiki/toolkit/csv2po. If you still have some issues please note that you need to make a _comma_ separated file. This is the format that the converter is expecting. Does OOo Calc give the option of choosing the delimiter style? Perhaps it is using the tabs because the initial file had them. Then you might need to open the file in a text editor and replace the tabs with commas. Take note of the expected file format that csv2po expects (three columns with source and target in the second and third columns respectively). It might be easiest to ensure that your file has this format, otherwise you will have to specify the format using the --columnorder parameter.

Q: How do I handle translation bugs?
A: Please read the process to follow at: http://wiki.services.openoffice.org/wiki/Handling_Translation_Issues. Also be careful before suggesting major terminology changes and carefully evaluate the impact the change will have. It will cause a major rework since all GUI strings, Online Help as well as all documetation will need to be readapted to the new terminology to make sure that the program is consistent in all its components.

Q: Can I use Pootle to translate the files for the 2.3 update release?
A: Currently, only Russian Italian and Khmer have been uploaded to the Pootle server hosted on the Sun virtuallab. Please see details at: http://wiki.services.openoffice.org/wiki/New_Translation_Process_%28Pootle_server%29
The 3 above languages are the only ones which will be using Pootle to translate the 2.3 version since we are in the initial/pilot phase. If everything goes well or at least we sort our the issues and we are able to fix them, all other languages and team that want to be added to this tool are more than welcome to join. That would be for the 2.4 release.

Q: During translation I see many strings already translated which do not match exactly with the English source: shall I leave them as they are or should I change them?
A: The translated strings you see need to be readjusted to reflect the English source. They are most probably translations of previous versions when the English source was different. Whenever an English string gets updated the translation of that string before modification is maintained because in most of the case it contains useful terminology that may be reused for updating the string. Sometimes the changes are really minimal, sometimes it's not the string but the tags in it which have changed or sometimes a typo in the English text has been fixed so that in the end you don't need to change anything in the translated text ... but sometimes you may need to retranslate the string completely.

Personal tools