Rainbow TKit - PO Package

From Okapi Framework
Jump to: navigation, search

Overview

The PO Package is one of the types of translation packages you can create with the Rainbow Translation Kit Creation Step. Such package can be post-processed using the Rainbow Translation Kit Merging Step.

In this package the input documents are extracted into corresponding PO files.

  • The first existing or leveraged translation is copied in the msgstr line and the entry marked as fuzzy.
  • Segmentation is currently not supported: Each text unit corresponds to a single entry in the PO file.
  • Inline codes are represented using placeholder similar to the ones used in OmegaT (e.g. <g1>/<x2/>/<b3>/<e3>).

The PO files generated in this package can be translated using any PO-capable translation tool.

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.po but each on its corresponding sub-directory.

Inline Codes

Inline codes are represented by letter-codes (similar to the ones used in OmegaT).

For example:

Text in <b>bold</b><br />
with a <a href='myfile.html'>link</a>.

is encoded as:

Text in <g1>bold</g1><x2/>
with a <g2>link</g2>.

This notation usually works well with MT engines such as Google Translate which is used in Transifex.

Segmentation

Currently the entries of the PO files are not segmented, even if the Segmentation Step (or another similar step) was executed before the Rainbow Translation Kit Creation Step.

Each entry corresponds to a "pararaph" entry in the original file.

Pre-Translation

Translatable entries can be pre-translted 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.

In addition, the first leveraged translation is also copied in the msgstr line and marked as fuzzy.

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.po
         +--- myFile.idml.po
         +--- subDir
              |
              +--- index.html.po
  • 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