SID configuration options
- SID vs. ICE priority settings
-
WorldServer allows the customer to control the order in which context-based matches are retrieved.
- disable/enable SID-based matching
- prefer ICE over SID-based matching
- prefer SID over ICE-based matching
Preferring SPICE matches over the standard ICE means that you want to establish more consistent, universal translations for content. The SID defines the context entirely, negating the normal match ranking strategy. Since there can only be one SPICE match for a given SID + Source text combination, there is no need for ranking. ICE matches become secondary, and are used only when SPICE matches are not available.
The preference options for ICE and SPICE matches may not result in significant leverage results in environments that almost entirely use SID-based content or in environments that use mainly non-SID-based content. For asset segments without associated SID values, WorldServer stores a copy of the translation for each asset. Currently WorldServer does not store asset-based entries for segments containing SIDs when the translation has not been updated.- TM configuration options
-
TM configuration options are defined in tm.properties, using the following entry:
prefer_sid_over_ice_matches=trueWhen SPICE matching is enabled, prefer it over ICE by default. If
true, look for SPICE match before looking for ICE match. Iffalse, seek ICE match first.