OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] Multilanguage DocBook documents - best practices needed


Thank you very much for the tip. I know OmegaT very well, my problem is not how to translate the docbook files, rather than how to handle the original xmls and the translated xmls so that both the books in the source language and its translations can be built without much effort.


On 07/18/2012 09:30 PM, Eric Streit wrote:


try to use OmegaT  and TMX format; it's what I use to translate my
docbook documents and it keeps the formating. It's a free tool (gpl).
They keep what is already translated in a databse (xml) and when you
encounter a phrase which is similar, they propose the most accurate
translation you already did.


XLIFF is another solution.

Le mercredi 18 juillet 2012 à 20:47 +0200, Fekete Róbert a écrit :
Hi Everyone,

I am in need for your experiences and advice about handling multilanguage DocBook documents (that is, documents in a master language and its translations).

We have a set of DocBook documents (books and articles) that are heavily modular (consisting of 50+ source files), and rich with xrefs, olinks, and screenshots. Currently we have three output formats, but we are planning to add new formats as well. Now these documents has to be translated - currently to one language, possibly to more in the future.

Another gotcha is, that this is is not a one-time translation, but should be maintained and updated about 3-4 times a year with the changes of the original document. (We do use version control.)

So my question is, do you have any recommendations on how to handle and manage the translation and multilanguage building of such a document set? What is the "best" way to organize the source files? I am looking for a solution that, for example, minimizes the risk of breaking links in the translated versions, and also does not require much post-processing on the translated files (except for generating the output files).

Also, since the translation will be done by an external translation agency (using computer-aided translation tools), storing the source text and the translations in the same file is not really feasible.

Any comment, tip, or recommendation is most welcome.

Kind Regards,

Robert Fekete

To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]