Rainbow Translation Kit Creation Step

From Okapi Framework
Jump to: navigation, search

Overview

This step creates a translation package from a set of input documents. The extracted files can be merged back after translation using the Rainbow Translation Kit Merging Step.

Takes: Filter events. Sends: Filter events or raw documents.

The simplest way to use this step is in a pipeline like this:

= Raw Document to Filter Events Step
+ Rainbow Translation Kit Creation Step

But you can perform other tasks before creating the translation kits. For example: segment the text and try to pre-translate it using different translation resource connectors.

= Raw Document to Filter Events Step
+ Segmentation Step
+ First Leveraging Step
+ Second Leveraging Step
+ Rainbow Translation Kit Creation Step

(Such pipeline is one of the pre-defined pipelines available in Rainbow).

Parameters

Package Format

Type of package to create — Select the type of translation kit you want to create. The following types are available:

- Generic XLIFF (The files are extracted to XLIFF documents)
- PO Package (The files are extracted to PO files)
- Original with RTF (The files get an RTF layer)
- XLIFF with RTF (The files are extracted to XLIFF then get an RTF layer)
- OmegaT Project (The files are extracted to a new OmegaT project)
- Transifex Project (The files are uploaded to a new or existing Transifex project)
- ONTRAM XINI (The files are extracted to an ONTRAM XINI package)
- Translation Table (The files are extracted to tab-delimited files)
- XLIFF 2.0 (The files are extracted to XLIFF v2 document)

Options — Click this button to edit the option specific to the type of package currently selected. Not all types of package have options.

More Info — Click this button to open the wiki page for the help on the type of package currently selected.

Send the prepared files to the next step — Set this option to send to the next step the prepared files as raw documents instead of the filter events of the original input file. Note that this option has no effect if the select package format that do not support one output file for each input file.

Output Location

Root of the output directory — Enter the directory where you want to create the package. You can use the variables ${rootDir} and ${inputRootDir}, as well as any of the source or target locale variables (${srcLoc}, ${trgloc}, etc).

Name of the package — Enter the name of the package directory to create.

Create a ZIP file for the package — Set this option to create a ZIP file from the generated package. The ZIP file has the same name as the project and is placed in the same directory with a .rkp extension.

Support Material

List of the files to include in the package — Shows the list of the support material items. Each item will be copied to its specified destination.

Add — Click this button to add an item to the list. After clicking on this button, click on Accept to accept the new item and add it to the list, or click Discard to cancel.

Remove — Click this button to delete the selected item from the list.

Origin — When adding an item: enter the path of the document or document set to copy. You can use * and ? as wildcard characters. For example C:\myProj\myExtra.* will copy all files starting with myExtra. of the C:\myProj directory into the destination. You can use the variables ${rootDir} and ${inputRootDir}, as well as any of the source or target locale variables (${srcLoc}, ${trgloc}, etc) in the origin.

Destination — When adding an item: enter the location of the copy of the original file in the package directory. The path must start with \ or / that indicates the root of the package's directory. use <same> to use the same filename as the original. If the origin does not use wildcard characters you can set a different name in the destination to rename the copy of the document. You can use the any of the source or target locale variables (${srcLoc}, ${trgloc}, etc) in the destination.

Limitations

  • If this step is used in a pipeline that modifies the input file (e.g. with a Search and Replace Step), the "original" files saved in the generated project may not be usable to merge back the translated files. For example, a search and replace may result in more or less inline codes. You would need to change those files so they reflect the content that was really used at the point the content was extracted.