Understanding the use of the update (or write) TM
In the configuration of the TM group, the user must specify which TM WorldServer should use to store new or updated translations. Translations are stored in the TM for each asset that is translated. If a new asset is leveraged fully against the applied TM group or if it is newly translated, then new translation entries will be generated for each segment when the asset is saved to the TM. These new TM entries will be stored into the write TM. If the same asset is re-leveraged after being updated, then new TM entries will be generated for the segments that have been newly translated or whose translation has been updated. Therefore, the new and updated translations will be stored in the write TM.
The system recognizes when the TM entry used to leverage a segment is already associated with the asset being leveraged. This is generally the case when working with a new version of a previously translated asset. Because the TM group is treated as a single entity, the default behavior does not consider from which TM the TM entry came, but only that there exists a TM entry in the TM group for the segment and this asset. The fact that the TM entry leveraged for a given segment is already in the TM group with an association to the current asset will prevent it from being written to the write TM, even if it is not explicitly stored in the write TM. This default behavior results in a leverage and minimizes duplication of TM entries across the TMs within the TM group. All applied or leveraged TM entries will be in the TM group, but will not necessarily end up in the write TM.
Alternatively, the user can configure WorldServer so that the update-TM process will ensure that all saved translations are written to the write TM in the event that the specified write TM does not already contain the applied TM entry. The save_ice_match_segments property can be set to true in the tm.properties file to ensure that all saved translations end up in the target write TM. (If the TM entry already exists in the write TM, it is not updated unless the translation has been modified.) For information about the tm.properties files, see Configuring TM properties..