Translation Memory Services Component
WorldServer provides a component through which you can extend or override certain TM services. This allows you to tweak certain aspects of the translation memory behavior. The services currently exposed are:
- TM AIS Path Normalization – Impacts only how the TM views the AIS paths of documents, 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 the files as being the same asset.
For example, consider these two AIS paths:
/WebPages/version1/index.html /WebPages/version2/index.htmlA normalization component could normalize these paths by removing the “versionn” folder level, allowing WorldServer to recognize that both index.html files represent the same asset.
If the assets are thought to be the same, WorldServer saves only a single set of translations, and the old versions will be relegated to history. This process 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 functionality 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. Segments that are autotranslated are given a “machine translation” status.
WorldServer calls the path normalization and auto-translation processes during the leverage process.
Java documentation
com.idiominc.wssdk.component.tm