Segment matching settings

In the tm.properties file, you can configure whether you want WorldServer to prefer SID-based matches over ICE matches or vice versa. You can also enable or disable SID-based matching.

The property that governs segment matching settings is called prefer_sid_over_ice_matches. It works only when both SID-based matches and ICE matches are enabled (enable_sid_lookup=true and enable_standard_ice_lookup=true):
  • If you set the value of the prefer_sid_over_ice_matches property to false, WorldServer will look for ICE matches first. This involves preferring a more localized usage context of translation. If there are no localized ICE matches, you might still have SID-based matches; however, as soon as a localized ICE match is available, WorldServer will prefer it.
  • If you set the value of the prefer_sid_over_ice_matches to true, WorldServer will look for SID-based (also known as segment preferred in-context exact or SPICE) matches first. Preferring SPICE matches over the standard ICE matches means that you want to establish more consistent, universal translations for content. The SID defines the context entirely, negating the normal match ranking strategy. There can only be one SPICE match for a given SID + source text combination, so there is no need for ranking. In this scenario, ICE matches become secondary and are used only when SPICE matches are not available.