Home Portal

Skip to end of metadata
Go to start of metadata
The Prepare Packages functionality is an optional feature of XTRF–CAT tool (memoQ, Memsource and XTM) integrations which allows for creation of bilingual files, their download from and upload to the CAT tool.

(In SDL Trados Studio integration, however, it plays a different role. See: Prepare Packages Action in SDL Trados Studio Integration.)

Table of Contents

Explanation of terminology used in this article

An automatic action is an operation performed entirely by the system, which requires no project manager or vendor involvement. When the workflow job which includes the automatic action is started, the system instantly and automatically executes its designed work.

A job performed by a vendor is an opposite to an automatic action. It is a job executed by a human being, e.g. a translator, proofreader, etc.

Target files or clean files are ready (output) files that are deliverable to the customer in the same format as the original (source = input) files. Not to be confused with target bilingual files which can also be deliverable to the customer, but in a bilingual format for use in CAT tools (e.g. XLIFF, MQXLZ, Two Column RTF, etc.).

Job mapping is matching of jobs in XTRF with corresponding workflow steps in CAT tools.

Standard use of CAT tool integration – standard configuration – without using packages

Workflow example: translation only

This example shows how to configure a workflow with only one job performed by a vendor (translation):


 

The translation in XTRF must be mapped to a corresponding job in the CAT tool. It will then be executed in the CAT tool.

See below an example of job mapping configuration in a Memsource workflow definition (for memoQ and XTM these settings are very similar):


 

Workflow example: translation & proofreading

To configure more jobs performed by vendors (e.g. proofreading), just add them before/after translation:


 

They also must be mapped in order to be executed in the CAT tool.

Standard use of CAT tool integration – alternative configuration – still without using packages

Workflow example: translation only


 

If the "Prepare Packages" action is present, but the "File Type for Package Preparation" option is set to "None", the effect will be the same as if there were no "Prepare Packages" action.

See below an example of a memoQ workflow definition (for Memsource and XTM this parameter is available in the same place):


 

Like in the "standard configuration" example, the translation in XTRF must be mapped to a corresponding job in the CAT tool. It will then be executed in the CAT tool.

Workflow example: translation & proofreading

Like in the "standard configuration" example, to configure more jobs performed by vendors (e.g. proofreading), just add them before/after translation:


 

CAT tool integration used only for the purposes of creating bilingual and target files

It is possible to use the integrated CAT tools with the following scenario:

  • upload source files to task input,
  • create bilingual files with the integrated CAT tool (the two initial automatic actions),
  • send the bilingual files to vendors who will perform the jobs in the tools of their own choice,
  • vendor will upload the bilingual files to the job output,
  • the integrated CAT tool (with the final automatic action) will create target files.

Workflow example: translation only

This example shows how to configure a workflow with only one job performed by a vendor (translation):


 

The translation in XTRF must be mapped to a corresponding job in the CAT tool, even though it will not be executed in the CAT tool.

See below an example of job mapping configuration in a Memsource workflow definition (for memoQ and XTM these settings are very similar):


 

In the "File Type for Package Preparation" option a type of bilingual files should be selected. For all three analyzed CAT tools (memoQ, Memsource and XTM), the "XLIFF Bilingual" format can be selected. Additionally, in memoQ you can select "memoQ MQXLZ" (a memoQ-specific zipped XLIFF format) or "Two Column RTF". See below an example of a memoQ workflow definition (for Memsource and XTM this parameter is available in the same place):


 

Workflow example: translation & proofreading

Like in the previous "translation & proofreading" examples, to configure more jobs performed by vendors (e.g. proofreading), just add them before/after translation:


 

Mixed scenario: some jobs performed by vendors executed in the integrated CAT tool, some outside of it

It is possible to configure a workflow in a way that some vendors will work in the integrated CAT tool and others – in a tool of their choice.

Workflow example: translation (in integrated CAT tool) & proofreading (outside the integrated CAT tool)

This example shows how to configure a workflow with one job (translation) performed by a vendor in the integrated CAT tool and another one (proofreading) performed by a vendor in a tool of their choice:


 

Both jobs (translation and proofreading) in XTRF must be mapped to corresponding jobs in the CAT tool, even though proofreading will not be executed in the CAT tool.

In the "File Type for Package Preparation" option a type of bilingual files should be selected. For all three analyzed CAT tools (memoQ, Memsource and XTM), the "XLIFF Bilingual" format can be selected. Additionally, in memoQ you can select "memoQ MQXLZ" (a memoQ-specific zipped XLIFF format) or "Two Column RTF". See below an example of a memoQ workflow definition (for Memsource and XTM this parameter is available in the same place):


 

Standard use of CAT tool integration plus creation of target bilingual files at the end of the workflow

In all previous examples the task output consisted only of the target (clean) files, i.e. if you uploaded DOC files as input, you'd get DOC files as output, too.

However, it is possible to create also target bilingual files in additional to the clean files, or instead of them.

In both cases, in the "File Type for Package Preparation" option a type of bilingual files should be selected. For all three analyzed CAT tools (memoQ, Memsource and XTM), the "XLIFF Bilingual" format can be selected. Additionally, in memoQ you can select "memoQ MQXLZ" (a memoQ-specific zipped XLIFF format) or "Two Column RTF". See below an example of a memoQ workflow definition (for Memsource and XTM this parameter is available in the same place):


 

Workflow example: translation only with only bilingual files in output (with Prepare Packages)

For this scenario, the only necessary change in the standard workflow definition is adding the Prepare Packages action after the External Project Finalization:


 

Workflow example: translation only with only bilingual files in output (with CAT Tool Action)

This scenario works in XTRF from version 2014 Summer (3.3).

For this scenario, instead of the External Project Finalization and Prepare Packages actions, the CAT Tool Action should be used which can replace both of them.

The CAT Tool Action can be created in the Configuration module, Workflows section, Automatic Actions subsection. The parameters of the action should be set like on the screenshot:


 

Note that in the "Fetch Packages from CAT Tool" option you can select a different bilingual format, depending on your needs and the CAT tool used.

The action should then be added to the workflow as the final step, after the last step that is performed by a vendor:


 

Workflow example: translation only with both clean and bilingual files in output (with Prepare Packages)

For this scenario, two bundles will need to be created:

  • the standard bundle for all files should be assigned as Read/Write to all jobs except the Prepare Packages job to which it should be assigned as Read Only
  • the additional bundle for target bilingual files should be assigned (as Read/Write) only to the Prepare Packages job

See the schema for this scenario:


 

And the bundle settings in XTRF:


 

Note that it is possible to have more bundles, e.g. a separate (Read Only) bundle for reference files, separate bundles for TMs and TBs, more bundles for work files each of which can be assigned to jobs differently etc. The above example presents the simplest configuration possible.

Workflow example: translation only with both clean and bilingual files in output (with CAT Tool Action)

This scenario works in XTRF from version 2014 Summer (3.3).

For this scenario, instead of the External Project Finalization and Prepare Packages actions, the CAT Tool Action should be used which can replace both of them.

Unlike in the version with two separate actions (in older versions of XTRF), there is no need for creating two separate bundles.

The CAT Tool Action can be created in the Configuration module, Workflows section, Automatic Actions subsection. The parameters of the action should be set like on the screenshot:


 

Note that in the "Fetch Packages from CAT Tool" option you can select a different bilingual format, depending on your needs and the CAT tool used.

The action should then be added to the workflow as the final step, after the last step that is performed by a vendor:


  • No labels