Documentation Center

Importing TM content

You can import TM content from other TMs.

Before you begin

  • Ensure that the TM content you want to import is stored in *.tmx, *.sdltm, *.zip, *.tmx.gz, *.sdlxliff format.
  • Ensure that the *.zip consists only of one *.tmx file, if you choose this format.
  • Ensure that each file you import has a maximum size of 1 GB, if you upload individual files. If you upload a *.zip archive, the individual files inside the archive can exceed 1 GB, but the *.zip archive must not exceed 1 GB. Note that, in the case of *.tmx, the *.zip can consist only of one file.
  • Ensure that the size of the TUs you want to import does not exceed 2000 characters for source and target segment (each, not combined).
  • Ensure that you configure your memoQ .tmx files properly to ensure that your fields are imported correctly. First, make sure that the fields you want to import from your memoQ .tmx file to your target TM are also present in the target TM. Second, make sure you add the x- prefix to your fields, in the memoQ .tmx file.

About this task

Usage: You can import TM content in a TM even if the TM is currently in use in a started project.

Process: TMs are applied on the source files of projects automatically during the Preprocessing stage of a workflow, and more specifically during the Translation Memory Matching task. If the project is started and you imported content in a TM which that project uses:
  • The newly updated TM is applied on the source files if the project has not reached the Translation Memory Matching task yet.
  • The newly updated TM is not applied on the source files if the project has already moved beyond the Translation Memory Matching task. However, the newly imported content will be returned during lookup or concordance search.

Restrictions:

Importing a *.tmx file into a cloud TM - The *.tmx is imported correctly if it has the same source-target languages as the destination TM. If there are source-target language mismatches, the import completes, but the mismatched language pairs are not imported.

Importing an *.sdlxliff file or an *.sdltm file into a cloud TM - The *.sdlxliff and the *.sdltm files are imported correctly only if they have the same source-target languages as the TM. If there are source-target language mismatches between the files you want to import and the TM, the import fails.

Procedure

  1. Log in to Trados Studio cloud capabilities (by accessing this link: http://languagecloud.sdl.com/lc).
  2. Go to the Resources view.
  3. Select Linguistic Resources > Translation Memories.
  4. Select the check box corresponding to the TM you want to import content to.
  5. Select Import.
  6. On the Import into [TM name] page:
    1. Under General Options:
      1. Select Browse to upload the files you want to import.
      2. (Optional) Enter fields and their values if you want to update the imported TUs with the same metadata information in one go.
      3. In the Language Direction box, check that the language pair is correct.
      4. Under Options, select or clear the check boxes: Import translation units as plain text, Export invalid translation units, Recompute fuzzy index statistics.
      5. Under If target segments differ, select one of the available options: Keep most recent translation units (default), Add new translation units, Overwrite existing translation units, Leave existing translation units unchanged.
    2. Under Advanced Options:
      1. If you import content from a *.TMX file, decide how you want unknown fields to be handled. From the Unknown Fields box, choose an option: Add to translation memory, Ignore, Skip translation unit, Fail translation unit import.
      2. If you import content from an *.XLIFF, *.TMX or *TMX.GZ file, decide which units will be imported based on their status: Translated, Translation Approved, Signed Off, Draft, Translation Rejected, Sign-off Rejected.
      3. Decide whether you want to apply an existing filter during TM import. To learn more about how you can configure a filter, consult this topic.
      4. Optionally, you can apply values to specific TM fields during import. Enter the name of the TM field in the left-hand side of the table, and then enter the value of the TM field in the right-hand side of the table. The value you enter here, will automatically be applied to all TUs which have the specified TM field.
  7. Select Finish. Note that, if the TUs (translation units) you want to import already exist in the cloud TM, the system ignores them. In other words, all perfect duplicates are not imported. The data is kept in the TM import history for 7 days, after which it is deleted.

Downloading the list of failed TUs

If some TUs fail to be imported, these can be downloaded as a *.tmx file.

About this task

The failed TUs are of three types: Discarded Translation Units, Bad Translation Units, Error Translation Units.
  • Discarded Translation Units - This category includes the duplicate TUs which are merged, and the TUs which are recognized as a result of Trados-specific technology (Numbers, Dates/Times, Acronyms, Measurements, Alphanumeric strings) and which do not need to be in a TM.
  • Bad Translation Units - This category includes invalid TUs or TUs which cannot be read.
  • Error Translation Units - This category includes empty TUs or TUs which exceed the maximum allowed limit.

Procedure

  1. If there are failed TUs, you can download them as a *.tmx file immediately after import. A notification appears in the upper right-hand side of the screen. Select the notification to download the *.tmx file.
  2. If there are failed TUs, you can download them as a *.tmx file within 7 days of the import as follows:
    1. Go to the Translation Memories view.
    2. Select the check box of the TM of interest.
    3. Select Import > Import History.
    4. Identify the failed import in the list and select the download symbol.