Trados Import Step

From Okapi Framework
Jump to: navigation, search

Overview

This step imports a set of input files into a Trados TM.

Takes: raw document (*.tmw). Sends: raw document.

NOTE: Trados TMs supported by this step consists of 5 files each. However, only *.tmw files should be added to the input file list.

Note: This step is part of the Trados Utilities Plugin and is not included in the general distribution.
This step runs on Windows only and requires that Trados 7.x or Trados 2007 is already installed on your machine.

You can use an existing Trados TM or you can create one on the fly. You can chose to send the Trados TM to the next pipeline step.

NOTE: All the Trados steps options correspond to options available in Trados workbench. See the Trados documentation for futher explanation of each option.

Parameters

Use or create the TM you want to import into: — Specify the path to an existing Trados TM or to a Trados TM you want to create. You can use the variables ${rootDir} and ${inputRootDir}, as well as any of the source or target locale variables (${srcLoc}, ${trgloc}, etc).

Overwrite if it exists — Set this option to overwrite an existing TM. (This is the same as deleting a TM and re-creating it).

User ID — Enter the user ID to use with the TM.

TM password — If needed, enter the password associated with the user ID for the TM. Leave empty if no password is needed.

Existing translation units — Select the action to perform when importing a translation unit into an existing one:

  • Leave unchanged reject all imported translation units.
  • Keep most recent and Keep oldest uses creation date to determine if the imported unit should overwrite and existing unit.
  • Overwrite always imports the external translation unit and overwrites any existing translation.
  • Merge merges the imported translation units into the TM using a set of rules. NOTE: This option is significant and you need to know the effecs of your selection.

See the Trados documentation for details about each option.

Import format — Select the imput format.

Large import file (with reorganization) — Select this option to perform optimizations when importing larger (< 500 units) files.

Ignore new fields — Select this option to ignore new attribute and text fields. If unchecked these are added to the current TM setup.

Check matching sub-languages — Select this option if you do not want to import translation units where the sub-language portion differs from the existing TM. For example, English (United States) does not match English (United Kingdom) if the option is checked. Note: If this option is not set, the main language portion still needs to match. for instance you cannot import French units into a TM where the target language is German.

Locale variables

The locale variables you can use in the paths are the following:

  • ${srcLang} = Source language code as defined in the source Language field. For example: en-US.
  • ${srcLangU} = Source language code in uppercase. For example: EN-US.
  • ${srcLangL} = Source language code in lowercase. For example: en-us.
  • ${srcLoc} = Source locale code (language in lowercase, region in uppercase, with a _ separator). For example: en_US.
  • ${srcLocLang} = The language part of the source locale (in lowercase). For example: en.
  • ${srcLocReg} = The region part of the source locale (in uppercase). For example: US. Or empty if no region is specified.
  • ${trgLang} = Target language code as defined in the target Language field. For example: fr-CA.
  • ${trgLangU} = Target language code in uppercase. For example: FR-CA.
  • ${trgLangL} = Target language code in lowercase. For example: fr-ca.
  • ${trgLoc} = Target locale code (language in lowercase, region in uppercase, with a _ separator). For example: fr_CA.
  • ${trgLocLang} = The language part of the target locale (in lowercase). For example: fr.
  • ${trgLocReg} = The region part of the target locale (in uppercase). For example: CA. Or empty if no region is specified.

The names of the variables are case-sensitive. However, for backward compatibility, the first letter can be in uppercase (e.g. ${SrcLang}).

Any locale-related variable (i.e. has "Loc" in the variable name), has no predictable behaviour if the corresponding language code declared in the Languages and Encodings tab is not compatible with a locale notation.

Limitations

  • You can only import a set of files with the same format at the time.