AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
Avaya GIS Customer Documentation Standards
Writer guidelines for machine translation
To ensure high-quality machine translation outputs before post-translation human editing, use the following writing best practices:
Simple sentence structure
Ensure that each sentence contains one idea. Try to keep each sentence shorter than 25 words because this sentence length is the easiest for a machine to translate.
Consistency
The machine translation engine detects repeated phrases and accurately translates them. Write sentences consistently, especially when they are repeated multiple times. This consistency reduces costs.
Ensure that you also use consistent terminology and style throughout your documentation.
Clear terminology
Do not use terms that an international audience can misinterpret or that have different meanings in certain environments. For example, avoid the words domestic and foreign.
Follow conrefing guidelines
Conref complete sentences and common elements. Do not conref individual words or parts of a sentence. The machine translation engine cannot detect the content behind the conref. Therefore, it does not recognize this content as part of the phrase.
Avoid conditions for options
Avoid using conditions to provide a complex series of options. Complex conditions make your content difficult to read and maintain, and can result in low-quality translation outputs. All options within conditions are included in the translated strings.
Example
The following image shows an example of a step that uses conditions to modify the information for different products:
The machine translation engine interprets this as follows:
