Trados Cleanup Step

From Okapi Framework
Jump to: navigation, search

Overview

This step invokes the Trados Clean Up function in batch mode.

Takes: Raw document. Sends: Raw document

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.

The step takes a list of input documents (in formats supported by Trados) and run the Trados Clean Up function on them. It uses a specified TM or, if none is provided, it creates a temporary empty one.

For running an analysis using Trados, see the Trados Analysis Step.

For running a pre-translation and/or a pre-segmentation using Trados, see the Trados Translation Step.

Parameters

Use this existing TM — Set this option to run the analysis against an existing Trados TM. If this option is not set a temporary TM is created during the process and deleted afterward. If this option is set you must enter the full path of the Trados .tmw file to use. You can use the variables ${rootDir} and ${inputRootDir}, as well as any of the source or target locale variables (${srcLoc}, ${trgloc}, etc).

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.

Full path of the log file — Enter the full path of the log file to generate. You can use the variables ${rootDir} and ${inputRootDir}, as well as any of the source or target locale variables (${srcLoc}, ${trgloc}, etc).

Append to the log file if one exists already — Set this option if the log file exists and you want to add the log of this process to it. If this option is not set and the log file exists it is overwritten automatically.

Open the log file after completion — Set this option to open automatically the log file once the process is done.

Changed translationsNo update - Do not update the TM with existing translations in the document but remove the Trados specific markers. Update TM - Update the TM with the translations in the document and remove the Trados specific markers, Update document - Revert the translations in the document to those in the TM and remove the Trados specific markers. For more info regarding the "Update changed translations", see the documentation provided by Trados.

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

  • None Known