tm_score_capitalization_penalty | Defines the penalty to assess for each capitalization difference. This value does not necessarily represent a final score penalty because it is weighted by the number of occurrences. | Content Level | 0.01 |
tm_score_extra_placeholder_penalty | This value determines whether placeholders should be considered in the scoring process. It does not actually represent the applied penalty. There are two other properties that are reserved for this purpose. If the value is 0, then placeholders are omitted from the scoring process. Setting the value to a number greater than 0 results in the placeholders being used to affect the scoring. Setting this property to 0 is the same as setting both the tm_score_inner_placeholder_weight and tm_score_outer_placeholder_weight values to 0. | Content Level | 1 |
tm_score_inner_placeholder_weight | Defines the inner placeholder tag weight (word weight is 1.0). Allows the effective weight of embedded placeholders to be set. The effort in correcting placeholder placement may not be the same as correcting a word. This property allows the weight to be set to establish a relative weight to a word element. | Element weight | 0.25 |
tm_score_number_difference_penalty | Defines the number difference penalty. This value does not necessarily represent a final score penalty as it is weighted by the number of occurrences. | Content Level | 0.2 |
tm_score_number_weight | Defines the number weight (word weight is 1.0). Allows the effective weight of numbers to be set. The effort in correcting numbers may not be the same as correcting a word. This property allows the weight be to set to establish a relative weight to a word element. | Element weight | 0.2 |
tm_score_outer_placeholder_weight | Defines the outer placeholder weight (word weight is 1.0). Allows the effective weight of outer placeholders to be set. The effort in correcting placeholder placement may not be the same as correcting a word. This property allows the weight be to set to establish a relative weight to a word element. | Element weight | 0.1 |
tm_score_placeholder_sequence_penalty | Defines the penalty for non-matching sequence numbers. This value does not necessarily represent a final score penalty as it is weighted by the number of occurrences. | N/A | 0.01 |
tm_score_punctuation_penalty | Defines the penalty for punctuation/non-alphanumeric character differences. This value does not necessarily represent a final score penalty as it is weighted by the number of occurrences. | Content Level | 0.005 |
tm_score_same_stem_penalty | Defines the penalty to be applied when the words being compared are different, but have the same stem. This property is used only when word stemmers are supported. Words with the same stem are generally related, and should be treated as related. | Content Level | .2 |
tm_score_asset_mismatch_penalty | This penalty allows you to penalize a TM match if it is not associated with the asset that is being translated. When assets are translated, matches are created that associated with that asset. As a result, the next time the asset is translated, WorldServer is able to bias the selection of matches based on whether they are associated with the newer version of the asset. If this penalty is set to a value greater than zero, then the leverage process will also penalize matches that are not associated with the asset being translated. Take care when using this penalty, as it affects all matches except SPICE matches. Nonetheless, this option may be useful to you if your quality requirements must take the source asset into consideration when evaluating ICE and exact matches. If your intentions are to prevent ICE matches against matches from a different asset, then you should use the ICE restricting option instead. | Leverage Level | 0 |
tm_score_metadata_mismatch_penalty | This penalty allows you to penalize matches that do not have a complete set of matching values with the asset for all AIS-TM mapped attributes. Instead of using physically different TMs to partition translation data, metadata can be used. For instance, you can use a mapped attribute to track the product with which the TM entry is associated. If the products are significantly different in the terminology used or in the language, you might want to further restrict the extent to which translations are cross leveraged. The use of this penalty allows you to do that. | Leverage Level | 0 |
tm_score_multiple_exact_match_penalty | This penalty allows you to penalize exact matches that occur when there are other exact matches for the segment with differing translations. Exact matches are ranked using the same rules for ICE matches, and generally will provide the best available match. Nonetheless, perhaps the existence of multiple translations for a segment implies the introduction of a quality issue. There is already the option to detect multiple exact match segments; however, the target segment will still be populated with the system's best guess for the exact match. If you are not comfortable with WorldServer choosing the best exact match for you, you could choose to penalize such matches so that they would be available to the translator as high fuzzy matches (or whatever leverage level as dictated by the penalty) instead of them being positioned solely for review as an exact match. The use of this option requires that the view multiple exact matches option is enabled. This penalty does not affect ICE matches. | Leverage Level | 0 |
tm_score_whitespace_difference_penalty | Defines the penalty to be applied when there are whitespace differences between the source text of the segment and the source text of the TM match. This is a content based penalty, not a leverage level penalty. Value range should be between 0 and 1. | Content Penalty | 0 |
tm_score_unreviewed_match_penalty | This penalty is applied to a match that is being leveraged that does not have the ???Reviewed??? status. Depending on whether your WorldServer environment is using Live TM mode or not, you may have TM entries stored in your TM that do not have a reviewed status. Working in the non-Live TM mode, all matches stored to the TM are viewed. However, in Live TM mode, the stored TM entries may have various statuses, such as ???Reviewed???, ???Unreviewed??? or ???Rejected??? depending on what is happening within the project. (Refer to the documentation on Live Translation Memory.) This penalty is a good way to control how the leverage treats matches that do not have the ???Reviewed??? status. By default, non-reviewed matches will not result in ICE matches, but they may lead to 100% matches. This is generally all right, since 100% matches typically must be reviewed anyway. During the leverage process, matches resulting from these TM entries will lead to the target segment being auto populated because it is a 100% match.
Perhaps your treatment of 100% matches is different and your goal does not require 100% matches to be reviewed. In order to do this, you need to ensure that the 100% matches that get registered meet some baseline quality guidelines. In this case, you might want to minimally require that only 100% matches that have been reviewed. This minimal goal can be accomplished by setting the Unreviewed penalty to a value greater than 0.
Note: As you review the other leverage level penalties, there may be other opportunities for you to eliminate lesser quality 100% matches so that you end up with 100% matches that may not require further review, depending on your quality requirements.
This penalty affects all matches, including SPICE and ICE. If your intentions are to prevent ICE matches against unreviewed matches, then you should use the ICE restricting option instead. | Leverage Penalty | 0 |
tm_score_reverse_leverage_penalty | This penalty allows you to penalize all reverse leverage matches. In WorldServer, TM content can be leveraged in both directions???source to target, and target to source. This is referred to as bi-directional leverage support. The maximum leverage level supported for reversed leverage matches is 100%. If a reverse leverage match results in a 100% match, it is treated the same way a normal, forward leveraged match???it will be populated into the target segment. Depending on your quality metrics, this may or may not be acceptable. You may want them to only be treated as high fuzzy matches. If this is the case, then this penalty can be used to prevent reverse leverage matches from generating 100% matches, and thus, prevent the target segment from being auto populated with them during the leverage process. | Leverage Level | 0 |
maximum_target_length_penalty | Defines the penalty to be applied to a hit with a translation that is too long | Leverage Level | .01 |
sid_mismatch_penalty | Determines penalty for SID mismatch condition. (0.0 - 1.0).
Rules:
- If both source and TM match have SID values, if different, then apply penalty
- If neither have SID values, no penalty
- If source has SID, and TM match does not, no penalty
- If source has no SID, and target does, apply penalty
| Leverage Level | 0 |