Before specifying any settings, you need to decide where to specify those
settings.
Specifying Translation
Memory Search Settings
You can specify translation memory search settings.
1.
Select All Language Pairs > Translation Memory and
Automated Translation > Search from the navigation tree. The Translation Memory >
Search settings are displayed on the right.
2.
Select your required search settings.
Use the these settings to specify how matching translation units
with formatting differences or multiple translations should be penalized.
1.
Select All Language Pairs > Translation Memory
and Automated Translation > Penalties from the navigation tree. The Translation Memory >
Penalties settings are displayed on the right.
2.
Select your required settings.
You can specify translation memory custom field values to assign to new translation units when updating the translation
memory. For example, if the
translation memory contains a field called Usage, you could assign the value, Printed
Guides to indicate that this translation should only be used for printed guides
as opposed to help.
NOTE
|
In order to assign custom field values to a
translation unit, the custom fields must already exist in the translation
memory settings. Click here for instructions on how to create translation memory custom
fields.
|
1.
Select All Language Pairs > Translation Memory and
Automated Translation > Update from the navigation tree. The Translation Memory >
Update settings are displayed on the right.
2.
Select your required settings.
Use the these settings to specify which language resource
templates is
used if there is no translation memory for a specific language pair selected
for that project. The language resource template is used to define the
segmentation rules and to identify untranslatable content.
1.
Select All Language Pairs > Translation Memory and
Automated Translation > Language Resources from the navigation tree. The
Translation Memory >
Language Resource settings are displayed on the right.
2.
Select your required settings.
No comments:
Post a Comment