The purpose of this article is to answer common questions about the Translation memory (TM) Export module in XTM Cloud and to help resolve issues you might experience with it.

Is it possible to export a set of TM data, containing segment IDs, in an XLSX file?

This is not possible. The segment IDs will not be visible in the generated XLSX file. However, if you generate a TMX file, for exporting the TM data, the segment IDs will be visible in the metadata .

Is it possible to export segments that contain a specific word from a TM?

This is not possible. You can only search for segments that contain a specific word in the TM Manage tab screen.

Is it possible to export a set of TM data that is restricted according to a specified creation date or modified date?

It is possible to do so via the REST API. For more information, see the official REST API documentation: XTM Connect SDK - REST API.

It is also possible to do so via the SOAP API by using the ExportTM method.

Are tags visible in an exported TM?

It does not matter how the tags have been created. Once a particular TM record contains some tags, they will be visible in the exported TMX file. The tags will all be visible in prop elements: <prop type="tagGroup">Example_tag</prop>.

Is it possible to export a TM with inline tags from XTM Workbench?

It is possible to export a TM with inline tags from XTM Workbench. To do so, you need to export your TM as a TMX file, which preserves all the data in it.

For example, you might then have the following text in the source file:

Which is shown in XTM Workbench in the following way:

The TMX export file will contain the relevant data.

What sets the order in which TM records are listed in a TM export file?

If the TM data is exported from a particular project that only contains segments that were not present in the TM (new TM matches), the TM records (segments) will be exported in the same order as they were listed in XTM Workbench. However, if the project consists of a mixture of new and existing translations (such as ICE matches or Leveraged matches), the order of exported segments will vary depending on factors such as time they were translated, type of TM match, etc.

Is it expected that a TMX export from projects have duplicated strings?

When Project Manager generates the TMX file at the project level (Project Editor → Files → TMX), the exported file will contain the translations and matches found for that project file. The limitations to what the TMX file should contain are only for Linguists, as you might not want them to be able to export all the data outside XTM Cloud.

To decide what level of details the Linguists should see in exported TMX files, select a relevant option from the TMX download options dropdown, in Configuration → Settings → Translation → Workflow and access → Linguist general options.

Open

It is expected that if a segment is translated and has a TM match, it will appear twice in this TMX export: once as a TM unit, and once as the translation from the file.

Is it possible to exclude specific projects from a TM export within a single XTM Cloud customer?

Excluding projects from a TM export is not possible in the XTM Cloud UI. The simplest way to do it would be to just export everything and then edit the file by deleting not needed entries.

As for the choice of a proper application used for opening the export file, it depends on what file type is used during export. The editing applications just need to be compliant with the file extension; for example, the XLF format is opened up Excel, whereas TMX goes well with any text editor.