Documentation Center

SID configuration options

You have some control over how segment matching is conducted.
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 the standard ICE matches means that you prefer the more localized usage context of translations. In this strategy, you might have SID-based matches that provide a default SPICE translation in the absence of a localized ICE match. However, as soon as there is a localized ICE match, it will be preferred.

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=true

    When SPICE matching is enabled, prefer it over ICE by default. If true, look for SPICE match before looking for ICE match. If false, seek ICE match first.

1 Storing a copy of each segment translation for each asset allows for identical content to be translated differently in different assets. This allows for historical assets to be retranslated in the same way as they were originally translated, even when the same content was more recently translated differently in another asset.