...
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 an XLIFF file, with its statuses, without
...
selecting the
...
"Import statuses" option in the XTM Cloud UI?
This is currently not possible. The said This option must be checkedselected. However, it is possible to do so in TMX files.
Can
...
the Modify the existing TM record if the project segment has the same setting be changed via the API? Example:
...
automated imports
...
have been scheduled. Each import should
...
be performed with a different setting. Can
...
the API be used to change the setting, run the import
...
and then restore the regular setting?
It is only configurable in the XTM Cloud global settings only, and there is no such option possibility to perform that kind of action via the API.
Is it possible to import a big file (190 MB
...
when zipped)
...
via the XTM Cloud UI?
In the XTM Cloud UI, there is a limit of 150 MB per file. Bigger files can be imported via the API or, if you do not have no license for it – an XTM Cloud license, we can support you in splitting a TMX file into smaller files.
...
Target language query (example): if a TMX file contains target language pt_BR
...
but
...
it is imported into the XTM Cloud UI
...
as pt_PT, will it import anyway?
Yes, 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 and choose target language “Portuguese” (pt_PT), the segments will be imported as “Portuguese” indeed.
Is it possible to import TM
...
in an XLSX file, together with all the metadata that
...
the file contains?
The only metadata possible to that can be imported via Excel is segment IDIDs, and the column containing it them must be named segmentid. Other metadata will not be imported; however. However, XLSX files can be converted to TMX through format using our internal tool.
...
When do language codes have to be accurate?
...
In a file name,
...
in an import file or somewhere else?
The language codes need to be accurate in the request itself, both for API import and for UI import the language codes need to be accurate (. (A list of all codes is available in the XTM Manual) in the request itself. Inside Cloud online help) . In the file, they must be placed as an attribute of tuv, and it is enough if they have only necessary to enter the first part of the language code.
For instance, you want to import TM data with source language en_US, and target language zh_CN and you have already chosen the language languages in the XTM Cloud UI. It is enough if inside the file the source language is set as to en , and the target language is set as to zh, in the file. The most important thing is to set it the languages correctly in the request. The file will not import at all if there the language codes set in it are completely different language codes inside from whatever you choose in the request. File The file name does not matter play a role at all.
...
When a TMX import file
...
fails to import, with errors
...
, how can I determine which segments
...
have not been imported and why the import failed?
Such errors are nearly always due to inline differences. To arrange to have for the file to be verified, and find out why import failed, raise a ticket with the XTM International Support team, on our Support Portal.