Post History

Source: https://writers.stackexchange.com/a/33542
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

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.

Original score: 8