Penalties in Studio-Aligned Mode
In Studio-aligned mode, translation activity tries to make sure that the content of the translation, including the markup tags used in the translation, are as accurate as possible. You can control how penalties are set and which penalty values are applied. With the penalty settings, you can avoid assigning a 100% match score in situations where you want to ensure that the translation proposal is reviewed and treated as a fuzzy match.
Penalties are primarily assessed for content and formatting inconsistencies. TM group penalties are applied as in the 9.x mode.
Content-based Penalties
If WorldServer automatically substitutes a piece of content during translation, it assesses a penalty on the translation unit. This penalty can be used to guarantee that (exact) matches produced by auto substitution are reviewed. The penalty is not triggered by tag-related auto substitutions. By default, the auto substitution penalty is set to zero (=0.00).
Metadata Penalty
The tm_score_metadata_mismatch_penalty setting in the tm.properties file extends 9.x mode behavior to the Studio-aligned mode. You have the option of applying the metadata mismatch penalty during WorldServer TM leverage when the metadata of the TM match does not match the metadata of the asset being translated. This is a global setting. The default is 0%.
To enable this penalty, you must map TM metadata to asset metadata:
- Create an AIS property with property type Text.
- Create a TM Entry attribute with the internal name matching the AIS property name. Set its attribute type to Text Field.
- Set map_ais_property_to_same_named_tm_attribute=true in the tm.properties file. The AIS property value will populate the value of TM attribute with the same name when the translation is saved.
- Set tm_score_metadata_mismatch_penalty=<number> in the tm.properties file.
<number> must be set to a number between 0 and 1. For example, tm_score_metadata_mismatch_penalty=0.02.
Formatting-related Penalties
There are two penalties related to formatting auto substitution and repair: the missing formatting penalty and the different formatting penalty.
- Different formatting penalty. Triggered if the markup tags in the translatable item source cannot be fully aligned with tags in the memory source segment.
- Missing formatting penalty. Triggered if the document source segment does not contain any tags, but the translation unit’s source segment does. In this case, all tags are dropped from the translation proposal and the penalty will be set (note that the different formatting penalty will not be triggered in addition).