Translation-oriented Authoring

Maximum efficiency in the composition of multilingual contents begins with the source text. For example, if the source text uses 200 different renderings for 100 technical terms – e.g., "hard drive" in one text and "hard disk" in another – translations into 10 languages would result in 2,000 target-language terms instead of the needed 1,000 terms.

For one thing, this impairs the consistency and quality of the documents. Even worse, it generates substantial extra expenses that are multiplied by the number of languages.

 

vergleichsrechnung_en_500 (58982 Byte)

 

Therefore, the objective is to compose the source text using wording that complies with defined linguistic standards and for which translations are already available.

For instance, if the sentence "Please observe the safety instructions" already exists in the translation memory, using this sentence enables the use of the corresponding translation from the translation memory; in contrast, using "The safety instructions must be observed" would call for a new translation.

For applications like MS Word, Adobe FrameMaker, and Just XMetaL, there are many plugins that allow ongoing interaction with the translation memory and terminology system of Across while writing, thereby facilitating the use of existing wording.

The recycling of language resources unfolds the greatest leverage in the source text, enabling the drastic reduction of translation costs and optimization of the text quality of all languages.

Required components for translation-oriented authoring with the Across Language Server:

Our Guided Tour provides a compact overview of the interaction of all components of the Across Language Server.

More detailed information on translation-oriented authoring is available in our white papers Translation-Oriented Authoring and Open Interfaces.