Export any TM from WorldServer, open it in an XML Editor and you will find these attributes (or most of them):
<prop type="x-idiom-source-ipath">
<prop type="x-idiom-target-ipath">
<prop type="x-idiom-next-hashcode">
<prop type="x-Projekt:SingleString">
<prop type="x-idiom-prev-hashcode">
<prop type="x-idiom-Segment-trans-Status">
<prop type="x-Comment:SingleString">
<prop type="x-Idiom-tm-uda-Import Job Id">
Now open the TMX file in Trados Studio and start the simple/quick conversion. After conversion, open the created Studio TM (*.sdltm): In the Attributes field you will notice that those attributes are not displayed.
Export the Studio *sdltm file back to TMX format and compare the original TMX exported from WorldServer with the one from Trados Studio: you will see that those attributes are gone.
This is quite critical because these attributes prevent important WorldServer metadata that is necessary to obtain ICE Matches.
The fundamental requirement for ICE matches is that the asset segment being leveraged most have at least one common surrounding segment (usage context) with the surrounding segments of the segment used to generate the TM entry. This information is captured within the TM entry as the prevHash and nextHash property values. The other values also point to important metadata information that is critical to get the correct and highest possible TM leverage.
Many customers want to do TM Maintenance directly in SDL Trados Studio instead of WorldServer. However, if they do that, they lose those important WorldServer attributes after import, - which has a severe impact on TM leverage.
