Is your content translation-friendly? Part 1

An object in a photograph cannot appear clean if it is dirty in reality. It is important that the source document for a translation is clear, precise and easy to understand for the translation to be all of these. When the source text succeeds in communicating the exact meaning to the translator, he/she can work on effectively expressing the same message in the target language. The lesser the challenges faced by the translator, the more the translation will be efficient in its intended application.

Most of the flaws in translation such as –

• Word-to-word translation,
• Ambiguity,
• Lack of exactness,
• Lengthy and complex sentences etc.

may indicate that the translator failed to understand what the source document had to say. If the source document i.e. the original document is unclear, the translator tends to stick to the dictionary equivalents of the words to avoid deviating from the source. There are language-specific styles articulated by certain unique expressions and are almost impossible to translate in another language. If the source document contains such expressions, the translation may become flat and ineffective.

How to write to ensure accurate translation of your document

Making sure that the document helps the translator to understand it is the biggest step towards receiving accurate translations. To save on the cost of going from one language into another, to reduce on the frustration of translators all over the world raising questions about your business literature and to finally enjoy the feeling of getting satisfactory service that you paid for, here are some tips to make your source documents translation-friendly.

Structure:

If a document is developed following definite and logical path, it is understood better. The structure of a document refers to the manner in which it establishes, explains and concludes a topic. A well-structured and organized document is easily followed by the translator as well as the reader. As a thumb rule a document should evolve starting from the basic to the complex or from core concepts to the circumferential ones.

The translator may not always have background knowledge of your project. At times, the actual translator of your document may not be a part of any of your meetings. So, for him/her the first source of information about the project is the document itself. If the document has logical linking between various topics that it contains, it helps the translator to better visualize what is being said in it.

Pointers to remember:

• Define the structure keeping in mind the type and size of your document as well as the available space.
• Outline the document structure: e.g. if you are writing about a product, here is a basic structure that the document can follow.
• Follow a progression that is universally understood.

Example: A product brochure/documentation can have the following sub-topics and sequence Introduction --> Purpose --> Basic Features/basic functions --> Usage instructions --> Precautions --> Maintenance and servicing --> After sales service and support

Terminology