XLIFF

From Ocelot
Jump to: navigation, search

This page describes how XLIFF is used in Ocelot.

Contents

XLIFF 1.2

Ocelot has supported XLIFF 1.2 since version 1.0.

ITS 2.0 metadata

Much of Ocelot's functionality is driven by ITS 2.0 metadata.

LQI

Ocelot reads and writes Language Quality Issue data according to the ITS 2.0/XLIFF 1.2 mapping. LQI metadata can be used to flag and filter segments, using Rules. New LQI issues can be added manually or via hotkeys.

Provenance

Ocelot reads and writes provenance data according to the ITS 2.0/XLIFF 1.2 mapping. Provenance data can be used to flag and filter segments, using Rules.

If the user has configured profile metadata (via File > Profile), Ocelot will automatically add it as a provenance record to any segment modified by the user. This includes segments where the target is modified, as well as segments where LQI metadata is added or modified. Ocelot writes out its provenance records using the RevPerson, RevOrg, and RevTool fields.

MT Confidence

Ocelot reads MT confidence data according to the ITS 2.0/XLIFF 1.2 mapping. MT confidence metadata can be used to flag and filter segments, using Rules.

Previous Target information

Ocelot stores "original target" information in alt-trans elements for segments that have been modified. The alt-trans elements that Ocelot creates for this purpose will tool attributes with the value "Ocelot". When Ocelot opens an XLIFF file, it will look for alt-trans with a tool value of "Ocelot"; if it finds one, it will use the target of that alt-trans to populate the "Original Target" column of the segment table. Other alt-trans elements will be ignored.

State Qualifiers

Ocelot recognizes certain values for the state-qualifier attribute of text-unit targets. Users may define State Qualifier Rules to highlight segments in those states in a particular color. Additionally, segments may also be filtered in the UI based on state-qualifier value. The supported state-qualifier values for these features are id-match, exact-match, fuzzy-match, and mt-suggestion.

Phase information

Ocelot recognizes certain values for the phase-name attribute of text-units. Ocelot will not allow new LQIs to be added to text-units with a phase-name value of "Rebuttal" or "Translator approval". Similarly, existing LQI on those issues can't be modified, with the exception of the comment field.

XLIFF 2.0

Ocelot doesn't currently support XLIFF 2.0, although it is planned for late 2014/early 2015.

Support for Other XLIFF 1.2 Implementations

Different tools handle different XLIFF 1.2 elements and attributes differently. Additionally, not all tools handle ITS metadata. If you've tried using Ocelot with XLIFF produced by another tool, let us know.

  • XLIFF 1.2 translation kit data exported from GlobalSight for use with OmegaT reportedly works fine with Ocelot.
  • XLIFF 1.2 translation kit data exported from WorldServer can be processed fine by Ocelot, although Ocelot ignores WorldServer's custom extensions. However, WorldServer does not support ITS metadata, so ITS data must be stripped from the XLIFF before it can be re-imported into WorldServer.

File Extensions

In Ocelot 1.1, Ocelot will only open files with the .xlf file extension. In future releases, Ocelot will also support the .xliff extensions (see OC-28).