WorldServer: How to find the context of a match in order to determine why the match is not an ICE match

The re-translated asset is not receiving ICE matches for all segments. While the great majority of the segments are ICE matches a few are 100% matches. Is this a correct result?

To verify why you are not getting an ICE Match:

1- Recreate the segmentation of the source asset used to produce the TM entry that is being leveraged.
2- Compare the previous and next segment of the appropriate common source record of the two assets (check the entry origin corresponding to the TM entry to find the path in Explorer).
3- If neither of them is identical then the TM match can not be an ICE match.

Important! Remember to check if SIDs have been used for either of the entries

The TM entry being leveraged and the active TM entry do not have at least one of the previous and next segments being the same. The relevant default setting in tm.properties is:

require_full_usage_context_for_ice=false

Note: if this property is set to true, to achieve an ICE Match, both the segment before and after must be the same in the new asset compared to the previously translated asset.

This article is relevant:

WorldServer - how to control the behavior of ICE Matches and set Penalties where required