Importing a single Translation Memory file into XTM Cloud
Using the XTM Connect – Bridge for Translation Memory variant, you can import single Translation Memory files into XTM Cloud in TMX format, or a ZIP file containing multiple TM files (see Importing multiple Translation Memory files into XTM Cloud).
Single TM files are processed and sent to XTM Cloud as follows:
The Translation requester manually uploads a translation memory file in
.tmxformat to the specified directory on the dedicated server.To ensure that TMX files are assigned to the correct customer, in XTM Cloud, and used for the correct language pair, this path format is used:
<Dedicated server directory for TM import><Customer ID><Source language name><Target language name><TMX file name>.Language folder names must only contain language codes with an underscore, eg. en_GB, de_DE or fr_FR.
Example:
/tm_import/2722/en_GB/de_DE/Christmas_promotion.tmxThis ensures that the correct TM data is made available for use in translation projects.
If additional processing has been configured, it is performed on the TM file.
XTM Connect – Bridge for Translation Memory fetches the translation memory file from the specified directory on the dedicated server and exports it to XTM Cloud. XTM Connect – Bridge for Translation Memory will automatically copy a TM file that has been manually copied to the specified directory to XTM Cloud at the directory-reading time interval set in the XML configuration files.
If the import to XTM Cloud fails, XTM Connect – Bridge for Translation Memory attempts to perform the import again for the number of times set in the XTM Connect – Bridge for Translation Memory configuration.
TM file processing statuses
To show a TM file's processing status, a suitable prefix is added to its name:
Processing status | Prefix | Description |
|---|---|---|
Importing | IMPORTING_ | File import into XTM Cloud. By default, files that are imported into XTM Cloud are listed in the Example (fictional):
|
Error | CORRUPTED_ | Error while a file is being processed (additional processing or import into XTM Cloud). By default, errors are logged in the Example (fictional):
|