- 签证留学 |
- 笔译 |
- 口译
- 求职 |
- 日/韩语 |
- 德语
It is very unlikely that users will read the complete online help documents or software manuals. Therefore, style is not the most critical issue in the translation of help and documentation. It is more important to focus on consistency, technical accuracy, use of correct references to the software user interface, and delivering clear, concise translations.
Here are some guidelines on language and style in online help translations.
Terminology
In most cases, the publisher will provide the vendor with a language style guide and terminology glossary. Always adhere to this terminology, and if there are issued with the terminology and style guide, these should be discussed with the publisher.
If no glossary is provided, create a terminology list with translations of frequently occurring terms or phrases in the source text. Ask the publisher to approve this terminology list before proceeding.
If the online help describes a software application, always use a software user interface glossary, and use the running localized software as a reference when translating an online help file.
Choose terminology which is consistent with the target operating system, such as Apple Mac OS or Microsoft Windows terminology.
Adaptations
If the source text contains country-specific statements which may require adjustment for the target language, for example, “1-800 phone numbers" for the United States, AM/PM time specifications, federal law restrictions, and local support contact information, ask the publisher for the relevant information for the target language or country.
Text and examples used in online help documents and illustrations should be culturally acceptable for the target language. If the examples contain many references to common U.S. sports or holidays, suggest alternatives to the publisher that are more appropriate to the target country or language.
In case of metric or other conversions, consult the publisher on the conversion standards to be used, and whether both metric and non-metric figures should be used in the translation.
Style
Many documents originating from the United States contain significantly more jargon, slang, and humor compared to documents written for non-U.S. markets. Always keep the target audience in mind when translating technical documentation, and adjust the style to suit local conventions.
In technical translation, it is recommended to use active voice, imperative form, and active verbs. Avoid passive style or sentences with many nouns. Try to avoid following the word order or syntax of the source language too closely.
Use a consistent style for certain standard text elements, such as headings. Most online help documents contain headings such as Printing documents", "Searching text", and "Indexing documents". Try to maintain the same level of consistency in the target language.
Agree on standards with the team of translators before the translation begins. Here are some issues that should be considered: