Translation for 2.4
This page summarizes useful information on the localization work needed for the OpenOffice.org 2.4 version. The native language teams working jointly with Sun Globalization on translation work are:
- Dutch Community
- French Community
- Germanophone Community
- Italian Community
- Spanish Community
- Brazilian Community
- Swedish Community
- Russian Community
- Chinese Community (for Simplified Chinese)
- Korean Community
- Japanese Community
- 1 Translation Schedule
- 2 Translating with SDF files
- 3 Translating with Pootle
- 4 Tips and Tools
- 5 Roles and Responsibilities
- 6 Q & A
- 1st translation hand off
09/27 - Translation start date
10/29 - Translation delivery date
GUI approx 700 words
Help approx. 15,000 words
- Interim Translation Delivery
11/26 - Deadline for the rest of the 1st hand-off translations (which are currently untranslated in Pootle)
11/26-11/29 - Import all the translations into the database and update Pootle contents with new strings for the 2nd hand-off
For UI statistics, please go to : http://www.sunvirtuallab.com:32300/projects/openoffice_org/
For Help statistics, please go to: http://www.sunvirtuallab.com:32300/projects/helpcontent2/
- 2nd translation hand-off
11/29 - Translation start date
12/20 - Translation delivery date
GUI approx. 1,200 words
Help approx. 13,800 words
Release Map with translation deadlines specific for the 2.4 release can be found at: http://wiki.services.openoffice.org/wiki/OOoRelease24
Translating with SDF files
- Sun creates l10n issues and attaches .sdf files as zip 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 Sun/G11n will take over conversion, please use issue to communicate conversion problems)
- Community translates the files using a translation .po editor
- Community sends the translated file to the Language Lead for review and corrections
- Language lead works with Community to finalize transalted files
- 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.4
In case linguistic review has not been performed right after translation:
- Language lead will carry out linguistic review after delivery
- Community will implement linguistic review results into translated files and deliver updated files 2 weeks after QA matrix delivery.
Issues containing .sdf files
- French: issue 82024
- German: issue 82025
- Dutch: issue 82027
- Brazilian Portuguese: issue 82026
- Simplified Chinese: issue 82066
- Korean:issue 82068
- Japanese:issue 82122 (files for translation) issue 83030 (translation completed SDF files)
Translating with Pootle
Teams translating with Pootle will need to follow the same translation schedule for 2.4. This will help finding out issues in time in this second pilot phase of this initiative.
- Pootle administrators make sure Pootle content is updated according to translation schedule
- L10n lead give the Go to start translation on Pootle (announcement to the dev@l10n list)
- Native Language leads make translation assignments following the Pootle User's Guide
- Translation teams work with Language team to make sure the translation is reviewed
- Native Language/translation leads make sure translation is complete within the deadlines
- Native Language/translation leads communicate translation completion to l10n lead
- Pootle administrator downloads the translated files and provide them to release engineering
It is recommended to use Pootle to manage the translation process and assignments. For translation it is recommended to download the files and translate them with a translation editor which support translation memory functionality. Linguistic review can be then performed right after translation.
Teams translating with Pootle
Tips and Tools
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.
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.
Latest TMX files can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx21/
SDF to PO Convertion 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.
Documentation with examples for conversion and backconversion can be found at: http://translate.sourceforge.net/wiki/toolkit/oo2po
PO files provided on the Pootle deployment for OpenOffice.org handle duplicate messages using KDE style (oo2po --duplicates=msgid_comment). Information on other styles used to handles duplicate messages is available here: http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle
It is important that if you are uploading and merging batches of PO content to the Pootle server that your content conforms to this style, otherwise it may not merge correctly with the content already present on the server.
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
|Language Lead||Central Engineer(s)||Project Lead||Other|
|Brazilian Portuguese|| Olivier Halllot
|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
|Berit Bonde||Petr Dudacek||Rafaella Braconi|
|Italian|| Andrea Pescetti
|Monica Badia||Petr Dudacek||Rafaella Braconi|
|Russian||Rail Aliev||TBD||Petr Dudacek||Rafaella Braconi|
|Spanish|| Santiago Bosio
|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|
|Korean|| Jeongkyu Kim
||Joy Zhang||Aijin Kim||Rafaella Braconi|
|Japanese|| Maho Nakata
|Reiko Saito||Naoyuki Ishimura||Rafaella Braconi|
Q & A
This session will be filled in with Q & As which will be raised and answered during the translation initiative
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.4 update release?
A: Please ask at the dev@l10n list for additional information. Please see details at: http://wiki.services.openoffice.org/wiki/New_Translation_Process_%28Pootle_server%29
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.