Length Restrictions and Pixel-Mapping

Max. and min. length restrictions (so far only supported for XLIFF 1.2 import files; also works across all segments of a trans-unit). Length restriction can be

• character based (number of characters)
• pixel based (number of pixel for a defined font and font size; used for translation of display texts)

Settings for a task can be done in the task-template.xml and pixel-mapping.xml (which must be included in the task's import-ZIP). Details see below.

Default settings must be provided in the config. Details see below.

Settings for Length Restrictions

General settings are  set in the task-template. These can be overwritten by each trans-unit.

• If maxNumberOfLines is set, maxLength refers to the length of each line, otherwise maxLength refers to the trans-unit (which might span multiple segments).
• maxNumberOfLines must refer to the lines in a single segment only! Trans-units must not span multiple segments then!

Settings for pixel-mapping

The mapping of characters and their pixel-lengths is given in pixel-mapping.xlsx.

Default values are set in the config.

Example for pixel-mapping.xlsx:
.

Trans-Unit

Example:

    <trans-unit id="4" translate5:maxNumberOfLines="2" minwidth="100" maxwidth="300" size-unit="pixel">
    <source>Example for maximal 2 lines, minwidth 100, maxWidth 300.</source>
    <target></target>
    </trans-unit>

Please note:

• translate5 uses translate5:maxNumberOfLines , not the maxheight-Element! (http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#maxheight).
  This is because with "pixel" as size-unit, the value of maxheight would refer to the pixel-height of the trans-unit, not to the number of lines.

Task Template

see Task Templates

Default Config