httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marion & Christophe JAILLET <>
Subject Doc translation: what about a new workflow?
Date Sun, 17 Apr 2016 05:20:20 GMT
Hi docs@,

a few weeks ago someone, a discussion [1] has started about using a web 
based application in order to translate our documentation.
The proposal was about Transifex [2].

Another tool that looks similar is provided by the Apache Foundation 
It works with Pootle. (see [3] which is the version used on t.a.o)

I don't know yet if our doc format is convenient for it.
At least, it can use .po files.
Tools exist to convert docbook (more or less our doc format) to .po 
files, handle translation and generate back some docbook document.
I have already used something called 'po4a' for such a process.

The workflow would be:
    main documentation in XML files --> generate/manage pot file --> 
generate/manage po files --> translate using t.a.o --> generate updated 
XML files for each languages --> generate html/pdf... as we actually do

The pros:
     - IMHO, following changes with po files is easier for translators
     - trunk/2.4.x are mainly the same files. They could be merged in 
the same po files to avoid duplication of translation effort
     - using po files keeps the document structure itself (formatting, 
links, ...). So the translator only has to focus on the translation of 
the text itself
     - translating is easier and can be shared easily between different 
     - easy access to translation statistic
     - svn integration

The cons:
     - the translator doesn't have a global view of the file he is 
working on
     - new tools and new intermediate file format
     - more complex doc generation process

Anyway, I think that our translation workflow is too complex.
Apart from the French translation (huge thanks, Lucien) and Spanish 
which sees some interest and looks promising (Thanks and welcome Luis), 
everything else is more or less dead.
So anything that ease access to new translators is a win.

We would like to have your feedback about the actual doc translation 
- Do you think that using XML files for the translation is convenient? 
Pros, Cons...
- Do you think that using .po files would help to keep track of 
translation changes?
- Do you think that using a web based interface for translation would be 
a win?
Any thought?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message