Professional Documents
Culture Documents
Translator Handbook
Globalization Team
Abstract
This document is intended to provide translators with EMC
specific information needed during translation.
Globalization Team
Document History
Published date
Version
V1.0
Changes made
First release
Author(s)
Approver(s)
Georg Kirchner
Globalization Team
Table of Contents
1. Introduction ................................................................................................................. 5
1.1.
Globalization Team
Table of Figures
Figure 1 - Formatting errors in Trados Studio .................................................................................. 7
Figure 2 - Verifying files .................................................................................................................. 7
Figure 3 - Verify files report ............................................................................................................. 8
Figure 4 - Minimum match value for TM searches........................................................................... 8
Figure 5 - Unused tags.................................................................................................................. 11
Figure 6 - Merging segments in Trados Studio .............................................................................. 13
Globalization Team
1. Introduction
1.1. Purpose, scope, and intended audience
This document provides technical guidance to translators who preform translation work for EMC
either in Trados Studio or in the TMS interface. For linguistic guidelines, consult the EMC
Localization Guides located in eRoom here.
Globalization Team
Globalization Team
Detailed results of the verification can be found under the Reports section. See Figure 3.
Globalization Team
Globalization Team
Globalization Team
Localized
Localized
Globalization Team
Globalization Team
When working in Trados Studio and TMS, source files are segmented, which is the key to
successful translation asset leveraging. Segmentation rules usually allow a sentence or a title to be
captured as one segment. However, in some cases, the author may have broken a sentence into
several segments (split segments). In some languages, the translation order of these split
segments has to be adjusted, causing translated segments not to match the source segments.
These are referred to as mismatched segments. Mismatched segments will corrupt Translation
Memories and therefore lead to incorrect translations when leveraging these TMs in the future.
Consider the following source sentence: Word1 Word2 Word3.
After segmentation, the sentence may look like in the following table. In an ideal situation, source
and target segments correctly match each other.
Source Segments
Target Segments
Word1 Word2
Word3.
Translation of Word3.
Target Segments
Word1 Word2
Translation of Word2
Word3.
To protect Translation Memories and avoid future leveraging problems, importing these
mismatched segments into TMs must be avoided by setting their segment status to Draft even if
these segments contain new or edited translations.
4.2.
When translating in Trados Studio, the translator can merge split segments to provide a complete
and exact matching translation. To do so:
1. In the Editor window, hold down the Ctrl key and click on the segment number column to
select the rows to merge;
2. Right-click on the segment number column of the last selected row and select Merge
Segments from the shortcut menu.
If there are any translations for the merged segments, those translations are also merged. See
Figure 6.
Globalization Team
If this functionality is used in Trados Studio but the project was a TMS project, the translator must
communicate this to the reviewer in the Review Handoff email, and clearly indicate the file name
and the segments involved. If the project is a non-TMS project, notification is not necessary.
Note
It is only possible to merge neighboring segments that belong to the same original paragraph.
If the segments do not belong to the same paragraph, or if the translation is done directly in the
TMS interface, the above-mentioned solution is not valid. In both of these cases, the translator is
required not to confirm the mismatched segments thus keeping them in Draft status. Those
segments will not be imported into the TM.
In this case, no notification must be provided to the reviewer.
Globalization Team
LCA
LiveContent Architect
LQE
PM
Project Manager
SLR
TM
Translation Memory
TMS