Difference between revisions of "Translation for 2.3"
| Line 3: | Line 3: | ||
The Communities who have adhered to this initiative are: | 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 == | == Schedule == | ||
| Line 18: | Line 18: | ||
* '''1st translation hand-off''' | * '''1st translation hand-off''' | ||
| − | + | Translation start date: June 7th <br> | |
| − | + | Translation delivery date: July 5th at noon CET <br> | |
* '''2nd translation hand-off''' | * '''2nd translation hand-off''' | ||
| − | + | Translation start date: July 12th <br> | |
| − | + | Translation delivery date: July 26th at noon CET <br> | |
| + | |||
Release Map with translation deadlines specific for the 2.3 release can be found at: | Release Map with translation deadlines specific for the 2.3 release can be found at: | ||
http://wiki.services.openoffice.org/wiki/OOoRelease23 | http://wiki.services.openoffice.org/wiki/OOoRelease23 | ||
| − | == Process == | + | == 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 | 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 | + | 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. | 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. | ||
| + | |||
== Tips and Tools == | == Tips and Tools == | ||
Revision as of 12:21, 7 June 2007
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!
Contents
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
Translation start date: June 7th
Translation delivery date: July 5th at noon CET
- 2nd translation hand-off
Translation start date: July 12th
Translation delivery date: July 26th at noon CET
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.
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:
Roles and Responsibilities
| Language | N-L Lead main contact(s) |
Language Lead | Central Engineer(s) | Project Lead | Other |
|---|---|---|---|---|---|
| Brazilian | Roberto Salomon Claudio Filho |
Augusta Marques Da Silva | Petr Dudacek Damien Donlon |
Rafaella Braconi | |
| Dutch | Arthur Buijs | Natalie Koning | Petr Dudacek Damien Donlon |
Rafaella Braconi | |
| French | Sophie Gautier | Jerome Roy | Petr Dudacek Damien Donlon |
Rafaella Braconi | |
| German | Jacqueline Rahemipour Marko Moeller |
Berit Bonde | Petr Dudacek Damien Donlon |
Rafaella Braconi | |
| Italian | Andrea Pescetti Alessandro Cattelan |
Monica Badia | Petr Dudacek Damien Donlon |
Rafaella Braconi | |
| Spanish | Santiago Bosio Alexandro Colorado |
Aridane Vilardane-Viegra | Petr Dudacek Damien Donlon |
Rafaella Braconi | |
| Swedish | Lars D. Noodén | Sofia Nilsson | Petr Dudacek Damien Donlon |
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. 300 words, Online Help approx. 22,000 words.
Q:
A:
