Difference between revisions of "ContinuousL10n"
From Apache OpenOffice Wiki
(Created page with 'Improved Localization Process thanks to the Continuous L10n The OpenOffice.org process has been changed into a continuous process which allows to provide l10n turnarounds cycles…') |
|||
| Line 1: | Line 1: | ||
| − | Improved Localization Process thanks to the Continuous L10n | + | == Improved Localization Process thanks to the Continuous L10n == |
The OpenOffice.org process has been changed into a continuous process which allows to provide l10n turnarounds cycles at every milestone. This process was presented at the OOoConf In Budapest: http://www.ooocon.org/index.php/ooocon/2010/paper/view/207 and is the outcome of Gregor Hartmann, Ivo Hinkelmann and Rafaella Braconi working on the so called "Continuous L10n" project. | The OpenOffice.org process has been changed into a continuous process which allows to provide l10n turnarounds cycles at every milestone. This process was presented at the OOoConf In Budapest: http://www.ooocon.org/index.php/ooocon/2010/paper/view/207 and is the outcome of Gregor Hartmann, Ivo Hinkelmann and Rafaella Braconi working on the so called "Continuous L10n" project. | ||
| Line 14: | Line 14: | ||
Take advantage of the Continuous L10n process to translate and verify immediately afterwards the translated strings in the product! | Take advantage of the Continuous L10n process to translate and verify immediately afterwards the translated strings in the product! | ||
| + | |||
| + | [[Category:Localization]] | ||
Revision as of 13:26, 14 January 2011
Improved Localization Process thanks to the Continuous L10n
The OpenOffice.org process has been changed into a continuous process which allows to provide l10n turnarounds cycles at every milestone. This process was presented at the OOoConf In Budapest: http://www.ooocon.org/index.php/ooocon/2010/paper/view/207 and is the outcome of Gregor Hartmann, Ivo Hinkelmann and Rafaella Braconi working on the so called "Continuous L10n" project.
The great advantages of this new workflow are that it automatically:
- creates a cws named l10n<workstamp><milestone> , e.g. l10ndev300m94
- downloads all translated files from Pootle
- downloads all sdf files found at ftp://qa-upload.services.openoffice.org/l10n/upload/ (no more sdf file delivery via Issue. Translated sdf files can be uploaded to this ftp)
- gsichecks and merges the translated sdf files
- builds language packs for all languages that have been changed (even when only 1 string has been changed) + one en-US build.
- removes languages from the build which cause a build error not covered by the gsicheck, this allowing other languages to be built.
- uploads the *_err.sdf from gsicheck
- uploads windows and linux32 languagepacks and the en-US insetsets to ftp://qa-upload.services.openoffice.org/l10n/download/
Take advantage of the Continuous L10n process to translate and verify immediately afterwards the translated strings in the product!
