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 following controls outside of the Browser Workbench affect translation memory matching:
- You can set the minimum percentage match that you want to appear in the Browser Workbench in
.
- 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
. See
Viewing or Modifying Translation Memory Entries in the online help.