I'd like to ask one more question. As we are using a CAT tool (OmegaT) we hope that we'll be able to re-use our TMXs for future translations of the documentation. That will only be possible if future versions of the published (and translated) chapters are very similar to the ones we are working on at the moment. How do you plan to update this documentation to future versions of OOo? It would be quite important for us (and for all using a CAT tool) if the structure and sentences used remain as similar as possible to the current version.

Thanks again,
Alessandro.

The advantage of a CAT tool is that the sentences that do remain the same will be flagged by OmegaT and will be very quick and easy to translate. So for the next version we will only need to translate the sentences that did actually change.
Cheers,
Jo

Thank you everybody for using OmegaT :)

I think Jo is correct, it is neither possible nor realistic to ask a writer to restrain oneself when updating a document. But the point of a CAT tool is exactly that the sentences that will have been changed will most probably match an earlier sentence in the memory and will be available for up-dating. As for the totally new items, they will sometimes match old material also because the matching algorythm is simple enough to take into account only words "forms" and not their meaning :)

I have been using OmegaT for a few years as a "professional" translator and never had to worry about big updates. CAT tools are useful within a document (to leverage repetitions within a single document) and also across documents (as is the case for updates).

I am sure by using Allessandro's group experience with OD, we'll be able to improve OmegaT so that it fits group translations better, especially in the context of OD files.

Jean-Christophe

Reply via email to