Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Introduction

The pre-processing option allows a project manager to create a project with a pre-processing workflow. This can be useful for:

  • locking segments, so they are not taken for translation;

  • editing the source text prior to analysis and translation (in this case the new source language is the same as the original source language);

  • using pivot languages (here the source language is first translated into one language, and then that target language becomes the new source for the translation into other target languages).


Guidelines

  1. As the user with the Administrator role, go to Configuration → Settings → Workflow → Workflow options → Pre-processing.

When pre-processing is enabled, you can select the default behavior during project creation:

  • No: → You can enable pre-processing during project creation, but it is disabled by default.

  • Yes, source segmentation: → The new source text segmentation matches the segmentation of the original source text.

  • Yes, new source segmentation: → The new source text is segmented based on the content provided during the pre-processing step. As a result, there may be a difference in segmentation between the pre-processing and the actual translation workflow steps.

2. When creating a project, enable Pre-processing as well as select a New source language in the Translation section.

3. Go to Workflow, select a linguist to translate from the source to the pivot (pre-processing) language and save the changes.

4. When the pivot translation has been finished, return to the workflow settings. You can now assign linguists for target languages and continue the standard translation process for your projects.

  • No labels