...

Introduction

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

...

Questions and answers

Is it possible to import XLIFF with its statuses without checking the option "Import statuses" in the XTM Cloud UI?

It This is currently not possible, the . The said option must be checked. However, it is possible to do so in TMX files.

Can you change the Modify the existing TM record if the project segment has the same setting via API? Example: there are scheduled automated imports, but each import should take place with a different setting. Can you use the API to change the setting, run the import, and then restore the regular setting?

It is only a global settingconfigurable in the XTM global settings only, and there is no such option to perform that kind of action via API. It is possible through the database.

Is it possible to import a big file (190 MB already zipped) through the XTM Cloud UI?

In the XTM Cloud UI, there is a limit of 150 MB per file. Bigger files can be imported through via API or if the client has you have no license for it - – we can use our internal tool to split support you in splitting TMX into smaller files.

If

...

a

...

Yes. For more information about duplicates management refer to this Excel document: Segment ID tests.

...

TMX file contains target language pt_BR, but in the XTM Cloud UI you import it as pt_PT, will it import anyway?

Yes, only it will import seamlessly. Only the first part of the language code, in this case “pt“, is taken into consideration. If you import it through the XTM Cloud UI, choosing target language “Portuguese” (pt_PT), the segments will be imported as “Portuguese” indeed.

Is it possible to import TM as XLSX together with all the metadata that is inside the file?

The only metadata possible to be imported via Excel is segment ID, and the column containing it must be named segmentid. Other metadata will not be imported; however, but XLSX files can be converted to TMX through our internal tool. In this case, write to the #help-support channel on Slack.

Is the imported TM stored anywhere in back-end?

It is available for a limited period in this path /xtm/xtm/temp/tmx, its name starts with “upload” and has the same name that it had in the import logs.

Where do language codes have to be accurate? File name, within the file, other?

For both API import and UI import the language codes need to be accurate (list of all codes is available in the XTM Manual) in the request itself. Inside the file they must be placed as an attribute of tuv, and it is enough if they have the first part of the language code.

For instance, you want to import TM source en_US, target zh_CN and you have already chosen the language in the XTM Cloud UI. It is enough if inside the file the source language is set as en and the target language is set as zh. The most important thing is to set it correctly in the request. The file will not import at all if there are completely different language codes inside than what from whatever you choose in the request. File name does not matter at all.

Import of the TMX import file failed with errors. How can I determine which segments were not imported and why the import failed?

Such errors are nearly always due to inline differences. To arrange to have the file verified, and find out why import failed, raise a ticket with the XTM International Support team, on our Support Portal.