Documentation Center

The translation memory services component

WorldServer provides a component through which you can extend or override certain translation memory (TM) services. By doing so, you can tweak certain aspects related to the behavior of the translation memory.

The currently exposed services are:
  • TM AIS Path Normalization – Affects only how the TM views the AIS paths of assets, and thus how the TM identifies assets as being different. The TM stores translations for each uniquely identified asset. If the AIS paths of two files appear to be the same after normalization, the TM will treat them as being the same asset.
    For example, consider these two AIS paths:
    /WebPages/version1/index.html
    /WebPages/version2/index.html
    A component could normalize these paths by removing the version<number> folder level, allowing WorldServer to recognize that both index.html files represent the same asset. If it recognizes the files as identical, WorldServer saves only a single set of translations and the old versions are relegated to history. This happens before each asset is leveraged.
  • Segment Auto Translation – This process determines when the source should be used directly to translate the target segment. This feature is executed during the asset leverage process. It is called only if the ICE, exact, and fuzzy match lookup processes all fail to return an acceptable match for the segment. Auto-translated segments receive the Machine Translation status.

WorldServer calls the path normalization and auto translation processes when calculating leverage.

Java package: com.idiominc.wssdk.component.tm