The updated TM
When you add or modify a TM sequence, you need to specify the TM where WorldServer should store new and updated translations. If you fully leverage a new asset against the applied TM sequence or if the asset has just been translated, WorldServer generates new TM entries for each segment when it saves the asset to the TM. These new TM entries are stored in the updated TM.
If you leverage the same asset again after updating it, WorldServer generates new TM entries for the newly translated segments and for the segments whose translation has been updated.
WorldServer 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 it treats the TM sequence as a single entity, the default behavior does not take into account the TM from which the entry came, but only that there is a TM entry in the TM sequence for this segment and asset. The fact that the TM entry leveraged for a given segment is already in the TM sequence with an association to the current asset will prevent it from being written to the updated TM, even if it is not explicitly stored in the updated TM. This default behavior results minimizes duplication of TM entries across the TMs within the TM sequence. All applied or leveraged TM entries will be in the TM sequence, but they will not necessarily end up in the updated TM.
save_ice_match_segments property to true in the tm.properties file. If the entries are already in the TM, it is not updated unless the entries have been modified.