Rainbow TKit - XLIFF with RTF

• Creation, Post-Processing and Manifest
• Package type: Generic XLIFF
• Package type: PO Package
• Package type: Original with RTF
• Package type: XLIFF with RTF
• Package type: OmegaT Project
• Package type: Transifex Project
• Package type: ONTRAM XINI
• Package type: Translation Table
• Package type: XLIFF v2

This package is one of the types of package offer by the Rainbow Translation Kit Creation Step.

It consists of standard XLIFF documents with an RTF layer on top. It can be useful for translation non-text-based source files that cannot be prepared by using just the original format with the RTF layer immediately on top of it, for example IDML files or DOCX files.

You can edit the such documents using any Trados-RTF compatible translation tool.

The post-processing step does both the conversion from RTF to normal XLIFF translated files, and their merging back into the original format.

Options

This package has no options.

Details

Sub-Directories

The extracted files are stored in the same directory structure as the original files, relative to the root of the file set.

For example if you have two files named index.html in two different sub-directories, they will be both extracted as index.html.xlf.rtf but each on its corresponding sub-directory.

Inline Codes

Inline codes are extracted as XLIFF inline codes and marked up with the tw4winInternal style.

Segmentation

Segmented entries are represented using the Trados-RTF notation, in the <target> elements.

Source text is marked as hidden text, while the translation is marked in normal style. Note that some of those segments may be empty if only some segments have been leveraged.

Pre-Translation

Translatable entries can be pre-translated different ways. In this package, the result of pre-translation is as follows:

• Existing translations marked as approved are put in the <target> element and the attribute approved is set to yes. These entries are also put in the approved.tmx file.
• Existing translations without flag are put in the unapproved.tmx file.
• Existing translations coming from alternate-translation constructs in the original file (for example the <alt-trans> elements of an XLIFF document) are put in the alternates.tmx file.
• Translations coming from some leveraging steps are put in the leverage.tmx file.

Package Layout

Assuming that your package name is pack1, your input root ends with main, the target language is French, you have selected to use the same filenames as the input files for the output files, and you have the following source files:

--- main
    |
    +--- index.html
    +--- myFile.idml
    +--- subDir
         |
         +--- index.html 

The layout of this package after creation will be:

--- pack1
    |
    +--- manifest.rkm
    +--- *.tmx
    +--- original
    |    |
    |    +--- index.html
    |    +--- myFile.idml
    |    +--- subDir
    |         |
    |         +--- index.html
    |
    +--- work
         |
         +--- index.html.xlf.rtf
         +--- myFile.idml.xlf.rtf
         +--- subDir
              |
              +--- index.html.xlf.rtf

• original contains a copy of the original source documents. You needs those files for post-processing.
• work contains the documents that are to be translated. The translation is expected to be saved into those files.

After post-processing it will be:

--- pack1
    |
    +--- done
    |    |
    |    +--- index.html
    |    +--- myFile.idml
    |    +--- subDir
    |         |
    |         +--- index.html
    |
    +... (same as after creation)

• done contains the merged translated documents. This directory is created during post-processing.

Limitations

• This package is BETA