7

In technical translation (e.g. of manuals), the quality of the source text often is not very high. This concerns not only the language used, but also the structure of the whole document.

Should technical translators rearrange the structure and overall layout of a document or should they keep the original structure and simply provide a sentence-by-sentence translation (as happens automatically when using translation software like OmegaT or SDL Trados Studio)?

migrated from techcomm.stackexchange.com Feb 20 '18 at 15:20

8

In the translation work I've seen for user-facing documentation, the translators stuck to the organization of the source but sometimes rephrased entire paragraphs, particularly if the source used idioms. This is particularly important if those translations need to be maintained over time as the source text is updated -- applying those updates to a translation that was rearranged will be both more expensive and more error-prone.

If there are problems in the source (you mentioned poor organization, for example), the best way to respond is to try to get those problems fixed in the source. This has the benefit of fixing it in at least two languages -- maybe more, if yours is not the only translation being done. My doc team occasionally receives requests for changes to make translation easier. We write with translation in mind to begin with, but nobody's perfect.

The general principle is to fix the problem as close to the source as possible. This is true whether you're talking about translation, formatting (single source, multiple outputs), or code.

  • 2
    Adding to @monica's comment, it's worth providing feedback about the source even if there are reasons to believe that it wouldn't be incorporated into the source during this revision cycle. The changes might show up in the next revision, or the principles behind the feedback might help improve the source for another project. Helping authors understand how their work can positively affect the quality and cost of translation is good for the long-term relationship. – Mike Rice Jan 24 '18 at 15:59
5

You mention manuals as an example. For these it may be down to the budget and the contract. For requirements documentation it is a different matter.

I have been involved in translations of requirements documents. These will contain clauses defining exactly how a system is to function once delivered. The document will almost certainly be referenced in a contract. These clauses will be explicitly tested by the customer and so must be retained and numbered identically in the translation.

It is necessary to translate as faithfully as possible, discuss the clauses with the original writer if at all possible.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.