Translation Memory Match Details

When you open an asset in the WorldServer Browser Workbench the target is populated with 100% matches, including in-context exact (ICE). WorldServer translation memory matches include the following:

An exact match is a match in all aspects of text: characters, punctuation and formatting. In an exact match, the text surrounding the source text might be different from the text surrounding the entry in a translation memory. (By contrast, a context match requires the same surrounding text.)

A 100% match has a score of 100%. A score of 100% is always an exact match. However, an exact match might not be a 100% match. (If the translation memory or translation unit is penalized, the score is reduced.)

A match can be scored as 100% without having been an exact match for one of the following reasons:

Configured penalties – WorldServer supports penalties that can affect the final score. Setting these penalties to zero will effectively instruct WorldServer to ignore certain differences between the source and lookup text.
Segment Repair – WorldServer provides a process through which repair heuristics can be applied to fix differences between the translation memory match and the original lookup text. In some cases, WorldServer can repair the translation memory match completely, and under certain conditions, the repair can lead to the final match being scored up to 100%.

During typical use of WorldServer, it is not always easy to differentiate between a 100% and an exact match. For scoping purposes, all 100% matches are grouped together. The Translation memory matches button in Browser Workbench presents a listing of all available matches.

An ICE match (in context exact match) is a type of exact match that is also a complete context match. If necessary, SDL WorldServer ranks multiple possible matches to find the most exact match, based on the most complete context matching.

When you are working in the Browser Workbench, and perform a save on the asset, it is saved in WorldServer.

The WorldServer Browser Workbench color codes the target segments to help you quickly assess which segments need the most work:

Color	Match Type	Description
Purple	In-context (ICE) match	The segment has a 100% match from translation memory that automatically populates the target. An in-context exact match occurs when a segment has been translated before, in the same segment of the same asset. When a segment has an in-context exact match, the target segment has a purple bar to its left. When a locking workflow is used, there is also a lock icon that appears, and the translator cannot modify that segment.
Blue	100% single exact match	The segment has 100% match from translation memory that automatically populates the target. A 100% match occurs when a segment has been translated before, whether in the same asset, or in a different asset with the exact same segment. When a segment has 100% match, the target segment has a blue bar to its left.
Double blue	Multiple 100% distinct exact matches	The segment has multiple distinct 100% matches from translation memory that automatically populates the target. A 100% match occurs when a segment has been translated before, whether in the same asset, or in a different asset with the exact same segment. When a segment has 100% match, the target segment has a blue bar to its left. When a segment has multiple distinct matches, the target segment has a double blue bar to the left, meaning the translation is different. By default, this feature is disabled because it affects performance during 100% matches. To learn about how to enable it, search for enable_bwb_multiple_exact_matches in the WorldServer Translation Memory Administration Guide.
Striped blue	Repaired 100% match	This state reflects a segment that has been repaired up to a 100% in context match. A 100% match occurs when a segment has been translated before, whether in the same asset, or in a different asset with the exact same segment. Translation memory can "repair" a match by adding or removing placeholders or numbers, thus creating up to a 100% match. When a segment has 100% match, the target segment has a blue bar to its left. When a segment has a repaired 100% match, the target segment has a dotted blue bar to its left.
Gold	Fuzzy match	The target segment contains a match from translation memory that is less than 100%. Fuzzy matches are not automatically populated into the target. You can choose Tools > Pretranslate to populate all empty targets in the document with the highest scoring match. When a segment has a fuzzy match, the target segment has a yellow-orange bar to its left.
Striped gold	Repaired fuzzy match	The target segment contains a repaired match from translation memory that is less than 100%. Fuzzy matches are not automatically populated into the target. Translation memory can "repair" a match by adding or removing placeholders or numbers, thus creating a fuzzy match. You can click the translation memory match button for the segment (pages icon) and populate the target on a segment-by-segment basis, or you can choose Tools > Pretranslate to populate all empty targets in the document with the highest scoring match. When a segment has a fuzzy match, the target segment has a yellow bar to its left. When a segment has a repaired fuzzy match, the target segment has dotted yellow-orange bar to its left.
Green	Manual translation	The segment has been manually altered by a user. When a segment is manually translated, it has a green bar to its left.
Dark red	Auto translation	WorldServer has determined the segment does not contain any translatable content. The source content was copied to the target side and the segment is considered to be translated. The rules for determining whether the content is translatable or not can be customized through the SDK and translation memory properties.
Blue-green	Machine translation	The Machine Translation marker indicates the segment has been populated from a match in a machine translation application.
Black	Repeated Segment	The repeated segment marker color denotes the first occurrence of a segment that is repeated within an asset or across multiple assets within the same project. Translating this occurrence can provide a translation entry in the translation memory that can be used to translate the other repetitions.
Black	Repetition	The repetition marker color denotes the segment as being a duplicate of a repeated segment. The actual segmented that is marked as being repeated may be located in the same asset or another asset within the same project.
Gray	Not translated	The segment may or may not have fuzzy matches available, but does not have 100% match and has not been altered by any user.

There are controls outside of the Browser Workbench that affect the TM matching:

You can set the minimum percentage match that you want to appear in the Browser Workbench in Tools > Personal Preferences .
In a large file (where there are over 100 segments on a page—which is possible if you have View all pages selected or have set Number of rows per page in tables to over 100 in your Personal Preferences), the system stops checking TM and TD matches per segment, to limit the number of queries being issued. In this case, a question mark is placed on the match indicator icon and you need to click on the item to see whether there are any TM or TD matches.
You can maintain your TM by removing obsolete matches, or modifying incorrect matches in Tools > Translation Memories . See Viewing or Modifying Translation Memory Entries in the online help.