SDL WorldServer - Segments marked as "MT!" are not shown as Machine Translated in the pre-translated file
000012710|6/3/2020 4:03 PM
We import a TMX file into a Studio Translation Memory. The TMX file contains TM entries coming from Machine Translation, created in a thirp Party tool (not in SDL Trados Studio). The TM entries coming from Machine Translation are with creation ID "MT!" as a creationID. Here is an example of the Content of the TMX file:
<seg>To that end, EASO takes due account of information already available from other relevant sources, as stipulated in the EASO Regulation, including EU+ countries, EU institutions, civil society, international organisations, and academia.</seg>
<seg>A tal fine, l'EASO tiene in debito conto le informazioni già disponibili da altre fonti pertinenti, come stabilito nel regolamento dell'EASO, compresi i paesi UE +, le istituzioni dell'UE, la società civile, le organizzazioni internazionali e il mondo accademico.</seg>
Studio has no problem importing the TMX file. After the import, we translate a source file using that TM. Studio recognized the origin of the TM entry as coming from Machine Translation and marks the TM entry accordingly. Also the segment leveraging from such a TM entry will display the entry origin as AT (Automated Translation) in the segment status, as displayed here:
However, if we import the same TMX file into WorldServer, create a project with the same file, the segments do not display the entry origin as AT (Automated Translation) or MT. The TM entry becomes a "normal" entry with no reference to its origin.
Unfortunately WorldServer does not have the capability to recognize the entry origin of TM entries after the import. Once imported in the Translation Memory, such TM entries will become regular ones. WorldServer will record the source and target text, the creation and modified date, the creator name, in this case "MT!", but it will not marked it as Machine Translated.
You can recognize the origin of such TM entries based on its creator name "MT!".
However, a segment with a TM leverage coming from such entry will display the fuzzy match and if you look up the TM entry, only the information related to the User who created and/or modified the TM entry. Such segments will not be displayed as MT segments either. Only segments that have actually been translated by a Machine Translation in WorldServer will retrieve that origin in the segment status. This screenshot displays the same segment and TM entry in WorldServer (Browser Workbench):
Consequently, when exporting a WSXZ package containing a TM with such TM entries, the segment status in Studio will not be AT, but 100% match or any fuzzy match, depending on the TM leverage.