L10n Wiki Process for Documentation
Contents
Information on Documentation for OpenOffice.org 3.0
OpenOffice.org docs to be localized for the next major release are:
- Basic Programming Guide The challenge with the localization of the Basic Programming Guide is that the content is currently published on the OOo wiki and will be also finalized there. For your reference here the link: http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide.
- Administration Guide (to be confirmed)
- Developer's Guide (only in English)
Localization Process for Wiki Documentation
| Task | Description | Notes |
|---|---|---|
| Authoring English doc with MediaWiki | ||
| Updating English doc | ||
| Community contribution to English doc | ||
| Review of contributions | ||
| Finalizing English docs | ||
| Handoff approach/process to l10n | ||
| Possible file formats to deliver to l10n | ||
| Translation methods (depending ex. on file format) | ||
| L10n handover approach/process to IPG | ||
| L10n handover approach/process to product team | ||
| Posting l10n documentation on wiki | ||
| Archiving l10n documentation |
Considerations
- Do the vendors see a possibility of translating directly using the wiki?
TPM: We should be able to track the changes in wiki, identify which part is updated by the community and review it, if needed. We can ask the vendor to update their translation memory according to the change. Though, it should be big burden for the checker and the vendor depending on the updated contents/volume by them.
Vendor: Technically yes. Though, we cannot use the translation memory then. We will have to:
1. Take the snap shot of the source contents
2. Translate the snap shot by using the translation tool
3. Back convert the translated contents
PM: We need to investigate how translation tools supporting mediawiki work for document translation. See OmegaT.
- Does the vendor prefer getting the wiki content exported into a odf file document?
Vendor: We can use a odf as the snap shot described above.
Vendor: If we have a document in odf file format, we can handle translation without problem.
- How do we track the differences between the previous version of the Basic programming guide and the Basic programming guide?
Vendor: We may use several ways to get the changes. one is whether the writer himself/herself has the change tracking info. second is to use previous TM to analyze the new file. third is to compare the pdf between two versions if pdf is available.
- How do we leverage what they have translated and still make sure that the translation matches the English text?
- Should the localized Guide match the English source?
- Do we want to fork l10n guides and English guides going forward?
Interim Solution
A graphic of the process we will be following can be found at OOo_Wiki_process
Note that for l10n we ill be working on a ODF snapshot of the English wiki. Changes to the English wiki document during l10n are inevitable but can be tracked with the history. Once the l10n document will be put back to wiki additional comments will be added to make sure the l10n version can be tracked to the corresponding English source wiki document.
Issues
MediaWiki to ODF export filter is still on progress. Still need to evaluate translation tools supporting MediaWiki (ex. OmegaT)
