XLIFF 1.1 Specification

Working Draft 2b, 10 Jan 2003

This version:
<not applicable yet>
Latest version:
<not applicable yet>
Previous version:
http://www.oasis-open.org/committees/xliff/documents/xliff-20020415.htm
Editor:
Yves Savourel <ysavourel@translate.com>
Copyright © 2001, 2002 The Organization for the Advancement of Structured Information Standards [OASIS].

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

 

Abstract

This document defines the XML Localization Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between tools.

Status of this Document

This document is the latest Working Draft of the committee for the XLIFF 1.1 Specification. It is an OASIS draft document for review by OASIS members and other interested parties. Comments may be sent to xliff-comment@lists.oasis-open.org.

This document may be updated, replaced, or rendered obsolete by other documents at any time. It is inappropriate to use this document as reference material other than "work in progress".

[Text to be added in version 1.1 is marked in green highlighting. Text that is 1.0 but is to be removed in 1.1 is marked in red highlighting. Draft notes (that will be removed in the final version) are in [brackets and yellow highlighting].]

Table of Contents

1. Introduction
2. General Structure
2.1. Header
2.2. Body
2.3. Named Groups
2.4. Extensibility
2.4.1. Adding Elements
2.4.2. Adding Attributes
2.4.3. Adding Attribute Values
2.4.4. Validating Documents with Extensions
2.5. Embedding XLIFF
3. Detailed Specifications
3.1. XML Declaration
3.2. Elements
3.2.1. Top-level and Header Elements
3.2.2. Named Group Elements
3.2.3. Structural Elements
3.2.4. Inline Elements
3.2.5. Delimiter Element
3.3. Attributes
3.3.1. XLIFF Attributes
3.3.2. XML Namespace Attributes

Appendices

A. XLIFF Tree Structure
B. Document Type Definition and Schemas
C. Changes Since Previous Version (Non-Normative)
D. Naming Guidelines (Non-Normative)
E. XLIFF Technical Committee (Non-Normative)
F. References

1. Introduction

XLIFF is the XML Localization Interchange File Format designed by a group of software providers, localization service providers, and localization tools providers. It is intended to give any software provider a single interchange file format that can be understood by any localization provider. It is loosely based on the OpenTag version 1.2 specification and borrows from the TMX 1.2 specification. However, it is different enough from either one to be its own format.

[The Naming Conventions section has been renamed and moved as an appendix]

2. General Structure

XLIFF is XML, as such it begins with an XML declaration. After the XML declaration comes the XLIFF document itself, enclosed within the <xliff> element. A XLIFF document is composed of zero, one or more sections, each enclosed within a <file> element. The <file> element consists of a <header> element, which contains meta-data about the <file>, and a <body> element, which contains the extracted translatable data from the <file>. The translatable data is contained within <trans-unit> elements in <source> and <target> paired elements. These <trans-unit> elements can be grouped recursively in <group> elements.

In addition, XLIFF provides the ability to maintain information about the processing of the file via the <phase> element. Possible translations for a specific <source> element can be generated from any number of MT (Machine Translation) and CAT (Computer Assisted Translation) systems and stored near the <source> in <alt-trans> elements. Context for a <source> that could be used by a translator or a TM (Translation Memory) system is provided by the <context> element. Binary data can be made available via the <bin-unit>, which may also be translated and contain an associated <trans-unit>.

The complete tree structure is available in Appendix A.

2.1. Header

The XLIFF <header> contains meta-data about the file and the localization process. It contains the <skl>, <phase-group>, <glossary>, <reference>, <count-group>, <tool>, <prop-group>, and <note> elements. The <skl> element contains either a skeleton file of the file submitted for localization or a hypertext link to that file.

The <phase-group> element contains information about each processing phase used in localizing the file; references to these phases are stored along with the translations. The <glossary> and <reference> elements may contain hypertext links to a glossary and reference file, respectively, or the actual glossary and reference data that can be used in the localization process.

The <count-group> element is a grouping element of count information of the entire file. The <prop-group> element contains tool-specific information used in combining the data with the skeleton file or storing the data in a repository. The <note> element contains instructions for the localization process. The <count-group>, <prop-group>, and <note> elements can also appear in the body of the file.

2.2. Body

The XLIFF <body> contains the structure and the localizable content from the file. It contains the <group>, <trans-unit> and <bin-unit> elements. The structure is described using the <group>, <trans-unit>, <bin-unit> elements. The <group> element is a general purpose structural element that allows describing the hierarchy of the file; it can contain other <group> elements as children as well as <trans-unit> and <bin-unit> elements.

The <trans-unit> and <bin-unit> elements are the leaf nodes of the tree structure. The <trans-unit> element contains the text to be translated, the translations, and other related information. The <bin-unit> contains binary data that may or may not need to be translated; it also can contain translated versions of the binary object as well as other related information.

In the <trans-unit> element the text to be translated is contained in a <source> element. This element may contain inline elements that either remove the codes from the source (<g>, <x/>, <bx/>, <ex/>) or that mask off codes left inline (<bpt>, <ept>, <sub>, <it>, <ph>). The translated text is contained in a <target> element that has the same inline codes available to it as does the <source> element. Translation matches generated by a TM or MT or entered by a translator may be provided in a <alt-trans> element, which also contains the <source> and <target> elements.

At every structural level contextual information for the localization process can be provided by the <context-group> named group element, count information by the <count-group> named group element, and tool-specific information by the <prop-group> named group element.

2.3. Named Groups

XLIFF allows grouping of certain elements into named groups. A named group is simply a grouping element with a name attribute. These named groups can be interspersed throughout the file with information designed for specific purposes. Using XML processing instructions different actions can be performed with specific named groups. The named group elements are <context-group>, <count-group> and <prop-group>.

The <count-group> element contains counts of words, translations, dialogs, or anything else that may need to be counted in the file. A different named group could be stored by the client, translator, reviewer, and localization engineer. Processing instructions could inform a system which of these <count-group> to update during the localization process.

The <prop-group> element contains tool specific data that can be used in creating the translated file, storing the translations, and any other specific task. Processing instructions can indicate to the tools which named <prop-group> to use when updating the repository or combining the localized data with the skeleton file to create a translated file. Note that the <prop-group> has been deprecated in version 1.1.

--- START NEW SECTION (2.4.*) --- [not highlighted for legibility]

2.4. Extensibility

At times, it may be useful to extend the set of information available in an XLIFF document by inserting constructs defined in various other XML vocabularies. There are several ways to do this in XLIFF. All of them use the namespace mechanism [XML Names]. You can add non-XLIFF elements, as well as attributes and attribute values.

Although XLIFF offer this extensibility mechanism, in order avoid a nimiety of information and increase interoperability between tools, it is strongly recommended to use XLIFF capabilities whenever possible, rather than to create non-standard user-defined elements or attributes.

2.4.1. Adding Elements

XLIFF provides several extension points in the following elements: <header>, <group>, <trans-unit>, <alt-trans>, and  <bin-unit>. Within each of these elements, the extension point is located just before the optional <note> elements; that is also just after where the optional <prop-group> elements (now deprecated) would be.

Several non-XLIFF element can be used at each extension point. The content of each element can be any valid XML content (empty content, PCDATA, mixed content, and so forth).

For example, the following XLIFF code shows how to add user-defined element (in bold) within an XLIFF document:

<xliff version='1.1'
 xmlns='urn:oasis:names:tc:xliff:document:1.1'
 xmlns:sup='http://www.ChaucerState.ac.pg/Frm/XLFSup-v1'>
 <file original='passus-1.doc' source-language='enm' datatype='plaintext'>
  <group>
   <sup:SourceInfo>
    <sup:Book>Piers Plowman, Passus 1</sup:Book>
    <sup:Author>William Langland</sup:Author>
   </sup:SourceInfo>
   <sup:WorkInfo Task='transcription' Context='Middle-English:1360'/>
   <trans-unit id='1'>
    <source xml:lang='enm'>What this mountaigne bymeneth</source>
    <target xml:lang='en'>What this mountain means</target>
    <sup:Reference Type='strophe'>1-a</sup:Reference>
   </trans-unit>
   <trans-unit id='2'>
    <source xml:lang='enm'>and the merke dale</source>
    <target xml:lang='en'>and the dark dale</target>
    <sup:Reference Type='strophe'>1-b</sup:Reference>
   </trans-unit>
   <trans-unit id='3'>
    <source xml:lang='enm'>And the feld ful of folk</source>
    <target xml:lang='en'>And the field full of folk</target>
    <sup:Reference Type='strophe'>2-a</sup:Reference>
   </trans-unit>
   <trans-unit id='4'>
    <source xml:lang='enm'>I shal yow faire shewe.</source>
    <target xml:lang='en'>I fairly will show.</target>
    <sup:Reference Type='strophe'>2-b</sup:Reference>
   </trans-unit>
  </group>
 </file>
</xliff>

The non-XLIFF elements used in the example above would be defined as the following:

<xsd:schema targetNamespace="XLFSup-v1"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:sup="http://www.ChaucerState.ac.pg/Frm/XLFSup-v1"
 elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xsd:element name="SourceInfo">
  <xsd:complexType>
   <xsd:sequence maxOccurs="unbounded">
    <xsd:element name="Book" type="xsd:string"/>
    <xsd:element name="Author" type="xsd:string"/>
   </xsd:sequence>
  </xsd:complexType>
 </xsd:element>
 <xsd:element name="WorkInfo">
  <xsd:complexType>
   <xsd:attribute name="Task" type="xsd:string"/>
   <xsd:attribute name="Context" type="xsd:string"/>
  </xsd:complexType>
 </xsd:element>
 <xsd:element name="Reference">
  <xsd:complexType>
   <xsd:simpleContent>
    <xsd:extension base="xsd:string">
     <xsd:attribute name="Type" type="xsd:string"/>
    </xsd:extension>
   </xsd:simpleContent>
  </xsd:complexType>
 </xsd:element>
</xsd:schema>

It is not possible to add non-XLIFF elements in neither the <source> and <target> elements. However, the <mrk> element can be used to markup sections of the text with user-defined values assigned to the mtype attribute. You can also add non-XLIFF attributes to most of the inline elements used in <source> and <target>.

2.4.2. Adding Attributes

Attributes of a namespace different than XLIFF can be included in several XLIFF elements.

The following elements allow non-XLIFF attributes: <file>, <group>, <trans-unit>, <source>, <target>, <bin-unit>, <bin-source>, <bin-target>, <alt-trans>, <mrk>, <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <ph>, and <it>.

For instance, the following XLIFF code illustrates how to use attributes from the XHTML vocabulary (in bold) in the the <group> and <trans-unit> XLIFF elements. The example show how to carry formatting information about the an extracted table:

<xliff version='1.1'
 xmlns='urn:oasis:names:tc:xliff:document:1.1'
 xmlns:htm='http://www.w3.org/TR/REC-html40'>
 <file original='table.htm' source-language='en' datatype='html'>
  <group restype='table' htm:border='1' htm:cellpadding='5'
   htm:cellspacing='0' htm:width='100%'>
   <group restype='row'>
    <trans-unit id='1' htm:valign='top' htm:width='30%'>
     <source>Text of row 1 column 1</source>
    </trans-unit>
    <trans-unit id='1' htm:valign='top' htm:width='30%'>
     <source>Text of row 1 column 2</source>
    </trans-unit>
   </group>
   <group restype='row'>
    <trans-unit id='1' htm:valign='top' htm:width='30%'>
     <source>Text of row 2 column 1</source>
    </trans-unit>
    <trans-unit id='1' htm:valign='top' htm:width='30%'>
     <source>Text of row 2 column 2</source>
    </trans-unit>
   </group>
  </group>
 </file>
</xliff>

In each of the XLIFF elements allowing non-XLIFF attributes: there is no specific location where to insert the non-XLIFF attributes, and there is no limit to the number of non-XLIFF attributes that can be used.

2.4.3. Adding Attribute Values

[NOTE: New text for extended attribute values. I have not managed to make work the XSD schema to validate "x-*" pattern (or XMLSpy doesn't work properly(?)]

Many attributes in XLIFF offer a list of enumerated values. Some applications may found necessary to add user-defined values to these lists. XLIFF allows for such extension.

The attributes where the list of values can be extended are the following: context-type, count-type, ctype, datatype, mtype, restype, size-unit, state, unit, priority, and purpose.

User-defined values must start with a "x-" prefix. There is no specified mechanism to validate individual user-defined values. The XLIFF schema will allow any value starting with "x-" in addition to the pre-defined values.

For example, the following excerpt shows how the user-defined value x-for-engineer can be utilized in a document:

...
<group>
 <context-group name='EngineersData'>
  <context context-type='x-for-engineers'>Data...</context>
...

2.4.4. Validating Documents with Extensions

In order to validate an XLIFF document that contains non-XLIFF parts, you can use the schema validation mechanism: In addition to the namespace declarations, add the schemaLocation attribute of the XMLSchema-instance namespace to define what schemas to use to validate the document (XLIFF and the non-XLIFF namespaces).

<xliff version='1.1'
 xmlns='urn:oasis:names:tc:xliff:document:1.1'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='
  urn:oasis:names:tc:xliff:document:1.1 xliff-1-1.xsd
  http://www.ChaucerState.ac.pg/Frm/XLFSup-v1 XLFSup-v1.xsd'
>
...
</xliff>

See http://www.w3.org/XML/Schema for more information on XML Schema and validation.

--- END NEW SECTION ---

--- START NEW SECTION (2.5.*) --- [not highlighted for legibility]

2.5. Embedding XLIFF

XML Namespace provides a convenient mechanism to use XLIFF constructs within another XML vocabulary.

If necessary an XLIFF document, or parts of a document can be embedded within another XML document. The only requirement for this is on the side of the XML format that includes the XLIFF data. For the document to be valid, it the schema of the given document type must include a definition for external elements.

If the including XML format uses XML Schema, it should include an <any> element in the definition of the element where the XLIFF data can be inserted. For example, the following XSD excerpt illustrates the case of an element type dataBlockType that can contain zero, one or more XLIFF constructs after a mandatory <type> element:

...
<xsd:complexType name="dataBlockType">
 <xsd:sequence>
  <xsd:element name="type" type="string" minOccurs="0"/>
  <xsd:any namespace="##other" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
 </xsd:sequence>
</xsd:complexType>
...

The ways of inserting different vocabulary in an XML document using XSD are described in section "Any Element, Any Attribute" in the document "XML Schema Part 0: Primer" available here: http://www.w3.org/TR/xmlschema-0/#any.

--- END NEW SECTION ---

3. Detailed Specifications

3.1. XML Declaration

The XML declaration is strongly recommended. It indicates the XML version and sets the defaults for the encoding of the file. For example, the following declaration specifies the document is in ISO 8859-1, the Latin-1 encoding.

<?xml version="1.0" encoding="iso-8859-1"?>

As in all XML files, the default encoding for an XLIFF file is assumed to be either UTF-8, which is a superset of the 7-bit ASCII character set, or UTF-16, which is UCS-2 with surrogate pairs for code points above U+FFFF. Thus, for these character sets, the encoding declaration is not necessary. Further, all XML parsers support these encodings. If the encoding is in UTF-16 the first character of the file must be the Unicode Byte-Order-Mark, U+FEFF, which indicates the endianness of the file. Other encodings may be desirable and may be generally supported by XML parsers. These must be declared using the encoding declaration. The values to use for the encoding declaration are defined in the [IANA Charsets] listing.

If necessary, you can also specify a namespace for XLIFF. The namespace identifier for this standard is "urn:oasis:names:tc:xliff:document:1.1".

A minimal XLIFF document with one entry looks something like this:

<?xml version="1.0"?>
<xliff version="1.1">
 <file source-language="EN" datatype="plaintext" original="file.ext">
  <body>
   <trans-unit id="1">
    <source>Hello World!</source>
   </trans-unit>
  </body>
 </file>
</xliff>

If you need to validate the document, use the schema validation mechanism: In addition to the namespace declarations, add the schemaLocation attribute of the XMLSchema-instance namespace to define what schema files to use. The same example as above would then look like this:

<?xml version="1.0"?>
<xliff version='1.1'
 xmlns='urn:oasis:names:tc:xliff:document:1.1'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='
  urn:oasis:names:tc:xliff:document:1.1 xliff-1-1.xsd
  urn:oasis:names:tc:xliff-values:document:1.1 xliff-values-1-1.xsd'>
 <file source-language="EN" datatype="plaintext" original="file.ext">
  <body>
   <trans-unit id="1">
    <source>Hello World!</source>
   </trans-unit>
  </body>
 </file>
</xliff>

For validating documents that include non-XLIFF namespaces see the section Validating Documents with Extensions.

3.2. Elements

XLIFF elements can be divided into five main categories: the top-level and header elements, the named group elements, the structural elements, the inline elements, and the delimiter elements. Attributes are shared among them.

Top Level and Header elements <xliff>, <file>, <header>, <skl>, <external-file>, <internal-file>, <glossary>, <reference>, <phase-group>, <phase>, <tool>, <note>.
Named Group Elements <context-group>, <context>, <count-group>, <count>, <prop-group>, <prop>.
Structural elements <body>, <group>, <reformat>, <trans-unit>, <source>, <target>, <bin-unit>, <bin-source>, <bin-target>, <alt-trans>.
Inline elements <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <sub>, <it>, <ph>.
Delimiter element <mrk>.

3.2.1. Top-level and Header Elements

The top-level and header elements are the following:

<xliff>

XLIFF document - The <xliff> element encloses all the other elements of the document.

Required attributes:

version.

Optional attributes:

xml:lang.

Contents:

One or more <file> elements.

<file>

File - The <file> element corresponds to a single extracted original document.

Required attributes:

original, source-language, datatype.

Optional attributes:

tool, tool-id, date, xml:space, ts, category, target-language, product-name, product-version, build-num.

Contents:

Zero or one <header> element, followed by
One <body> element.

<header>

File header - The <header> element contains data relating to the <file> element.

Required attributes:

None.

Optional attributes:

None.

Contents:

zero or one <skl> element, followed by
zero or one <phase-group> element, followed by
zero, one or more <glossary> elements, followed by
zero, one or more <reference> elements, followed by
zero, one or more <count-group> elements, followed by
zero, one or more <tool> elements, followed  by
zero, one or more <note> elements, followed by
 zero, one or more <prop-group> elements, followed by
Zero, one or more non-XLIFF elements, followed by

<skl>

Sekeleton file - The <skl> element contains the skeleton file or the location of the skeleton file.

Required attributes:

None.

Optional attributes:

None

Contents:

Either exactly one <internal-file> or one <external-file> element.

<internal-file>

Internal file - The <internal-file> element will contain the data for the skeleton file.

Required attributes:

None.

Optional attributes:

form, crc.

Contents:

An embedded file.

<external-file>

External file - An empty element that specifies the file location.

Required attributes:

href.

Optional attributes:

uid, crc.

Contents:

The <external-file> is an empty element, including attributes only.

<glossary>

Glossary - Element points to the glossary source.

Required attributes:

None.

Optional attributes:

None.

Contents:

The glossary description and either exactly one <internal-file> or one <external-file> element.

<reference>

Reference - Contains information about the reference material.

Required attributes:

None.

Optional attributes:

None.

Contents:

A description of the reference material and either exactly one <internal-file> or one <external-file> element.

<note>

Note - The <note> element is used to add localization-related comments to the XLIFF document. The content of <note> may be instructions from developers about how to handle the <source>, comments from the translator about the translation, or any comment from anyone involved in processing the XLIFF file.

Required attributes:

None.

Optional attributes:

xml:lang, from, priority.

Contents:

Text, no standard elements.

<phase-group>

Phase group - The <phase-group> element contains phase information. This phase information is specific to the users.

Required attributes:

None.

Optional attributes:

None.

Contents:

One or more <phase> elements.

<phase>

Phase information - The <phase> contains metadata about a particular version of XLIFF data.

Required attributes:

phase-name, process-name.

Optional attributes:

company-name, tool, tool-id, date, job-id, contact-name, contact-email, contact-phone.

Contents:

Zero, one or more <note> elements.

<tool>

Tool - The <tool> element allows to identify the tool that has been used to execute a given task in the document.

Required attributes:

tool-id, tool-name.

Optional attributes:

tool-version, tool-company.

Contents:

Empty.

 

3.2.2. Named Group Elements

The named group elements are the following:

<count-group>

Count group - The <count-group> element holds count elements relating to the level in the tree in which it occurs. Each group for <count> elements must be named, allowing different uses for each group.

Required attributes:

name.

Optional attributes:

None.

Contents:

One or more <count> elements.

<count>

Count - For each <count> element the the required count-type attribute would indicate what kind of count the element represents, and the optional unit attribute would indicate the unit of the count (by default: word). A list of values for count-type and unit is provided.

Required attributes:

count-type.

Optional attributes:

unit.

Contents:

Number (the count value).

<context-group>

Context group - The <context-group> element holds context elements relating to the level in the tree in which it occurs. Thus context can be set at a <group> level, a <trans-unit> level, or a <alt-trans> level.

Each <context-group> element must be named, allowing different uses for each group. These uses can be controlled through the use of XML processing instructions.

Because the <context-group> element may occur at a very high level, a default context can be established for all <trans-unit> elements within a file. This default can be overridden at many subsequent levels.

Required attributes:

name.

Optional attributes:

crc, purpose.

Contents:

One or more <context> elements.

<context>

Context - The <context> element describes the context of a <source> within a <trans-unit> or a <alt-trans>. The purpose of this context information is to allow certain pieces of text to have different translations depending on where they came from. The translation of a piece of text may differ if it is a web form or a dialog or an Oracle form or a Lotus form for example. This information is thus required by a translator when working on the file. Likewise, the information may be used by any tool proposing to automatically leverage the text successfully.

Required attributes:

context-type.

Optional attributes:

match-mandatory, crc.

Contents:

Text, no standard elements.

<prop-group>

Property group - The <prop-group> element contains <prop> elements. Each <prop-group> element may be named, allowing different uses for each group. These uses can be controlled through the use of XML processing instructions.

Important: The <prop-group> element is DEPRECATED in version 1.1. Instead, use attributes defined in a namespace different from XLIFF. See the Extensibility section for more information.

Required attributes:

None.

Optional attributes:

name.

Contents:

One or more <prop> elements.

<prop>

Property - The <prop> element allows the tools to specify non-standard information in the XLIFF document. This information can be used by the tools that have produced the file or that translate the file or that do any other amount of processing specific to the producer.

Important: The <prop> element is DEPRECATED in version 1.1. Instead, use attributes defined in a namespace different from XLIFF. See the Extensibility section for more information.

Required attributes:

prop-type.

Optional attributes:

xml:lang.

Contents:

Tool-specific data or text, no standard elements.

 

3.2.3. Structural Elements

The structural elements specify the frame of a XLIFF document as well as contextual and processing information. The <source> element contains the extracted data and, possibly, inline elements.

<body>

File body - The <body> element contains the structural elements.

Required attributes:

None.

Optional attributes:

None.

Contents:

Zero, one or more <group>, <trans-unit>, <bin-unit> elements in any order.

<group>

Group - The <group> element specifies a set of elements that should be processed together. For example: all the items of a menu, etc. Note that a <group> element can contain other <group> elements.

Required attributes:

None.

Optional attributes:

id, datatype, xml:space, ts, restype, resname, extradata, help-id, menu, menu-option, menu-name, coord, font, css-style, style, exstyle, extype.

Contents:

Zero, one or more <context-group> elements, followed by
Zero, one or more <count-group> elements, followed by
Zero, one or more <note> elements, followed by
Zero, one or more <prop-group> elements, followed by
Zero, one or more non-XLIFF elements, followed by
At least one of <group>, <trans-unit>, <bin-unit> elements in any order.
All <context-group>, <count-group>, <prop-group>, and <note> elements pertain to the subsequent elements in the tree but can be overridden within a child element.

<trans-unit>

Translation unit - The <trans-unit> elements contains a <source>, <target> and associated elements. Lists of values for the datatype, restype, and size-unit attributes are provided.

Required attributes:

id.

Optional attributes:

approved, translate, reformat, xml:space, datatype, ts, phase-name, restype, resname, extradata, help-id, menu, menu-option, menu-name, coord, font, css-style, style, exstyle, extype, maxbytes, minbytes, size-unit, maxheight, minheight, maxwidth, minwidth, charclass.

Contents:

One <source> element, followed by 
Zero or one <target> element, followed by
Zero, one or more  <alt-trans> elements, followed by
Zero, one or more <context-group> elements, followed by
Zero, one or more <count-group> elements, followed by
Zero, one or more <reformat> elements, followed by
Zero, one or more <note> elements, followed by
Zero, one or more <prop-group> elements, followed by
Zero, one or more non-XLIFF elements.
 All child elements of <trans-unit> pertain to their sibling <source> element.

<reformat>

Reformat - The <reformat> element is to indicate whether the target properties can be formatted (size, font, etc.) differently from the source. Use the element attribute to specify the name of the element content to reformat or not, or use the attribute attribute to specify the name of the attribute value to reformat or not. The attribute edit allows you to specify whether or not the given item is to be modified.

Example: 

<trans-unit id='1' restype='button' coord='8;8;54;14'>
 <reformat attribute='coord' edit='yes'/>
 <source>Accept</source>
</trans-unit>

Required attributes:

element or attribute, edit.

Optional attributes:

None.

Contents:

None.

<source>

Source text - The <source> element is used to delimit a unit of text that could be a paragraph, a title, a menu item, a caption, etc. 

Required attributes:

None.

Optional attributes:

xml:lang, ts.

Contents:

Text, 
Zero, one or more of the following elements: <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <ph>, <it>, <mrk>, in any order.

<target>

Target - The <target> element is used to delimit a unit of text. A paragraph in XLIFF does not necessarily correspond to a "paragraph" in a word-processor. It's simply a unit of text that could be a paragraph, a title, a menu item, a caption, etc. A list of preferred values for the restype attribute is available.

Required attributes:

None.

Optional attributes:

state, phase-name, xml:lang, ts, restype, resname, coord, font, css-style, style, exstyle.

Contents:

Text, 
Zero, one or more of the following elements: <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <ph>, <it>, <mrk>, in any order.

<alt-trans>

Translation match - The <alt-trans> element contains a possible translation in a <target> along with optional context, notes, etc.

Required attributes:

None.

Optional attributes:

match-quality, tool, tool-id, crc, xml:lang, datatype, xml:space, ts, restype, resname, extradata, help-id, menu, menu-option, menu-name, coord, font, css-style, style, exstyle, extype, origin.

Contents:

Zero or one <source> element, followed by
One or more <target> elements, followed by
Zero, one or more <context-group> elements, followed by
Zero, one or more <note> elements.
Zero, one or more <prop-group> elements, followed by
Zero, one or more non-XLIFF elements.
 All child elements of <alt-trans> pertain to their sibling <target> element.

<bin-unit>

Binary unit - The <bin-unit> element contains a binary object that may or may not be translatable.

Required attributes:

id, mime-type.

Optional attributes:

approved, translate, reformat, ts, phase-name, restype, resname.

Contents:

One <bin-source> element, followed by
Zero or one <bin-target> elements, followed by
Zero, one or more <context-group> elements, followed by
Zero, one or more <count-group> elements, followed by
Zero, one or more <reformat> elements, followed by
Zero, one or more <note> elements, followed by
Zero, one or more <prop-group> elements, followed by
Zero, one or more non-XLIFF elements, followed by
Zero or more  <trans-unit> elements.
All child elements of <bin-unit> pertain to their sibling <bin-source> element.

<bin-source>

Binary source - The <bin-source> element is the container for the binary source data.

Required attributes:

None.

Optional attributes:

ts.

Contents:

One of <internal-file> or <external-file>.

<bin-target>

Binary target - The <bin-target> element is the container for the translated version of the binary data.

Required attributes:

None.

Optional attributes:

mime-type, ts, state, phase-name, restype, resname.

Contents:

One of <internal-file> or <external-file>.

 

3.2.4. Inline Elements

The inline elements are the elements that can appear inside the <source> and <target> elements. They enclose or replace any formatting or control codes that is not text, but resides within the text unit.

<g>

Generic group placeholder - The <g> element is used to replace any inline code of the original document that has a beginning and an end and can be moved within its parent structural element. When possible, the ctype allows you to specify what kind of attribute the placeholder represents. A list of preferred values for the ctype attribute is available.

A <g> element can contain another <g> element. In this case, if the embedded group has an id attribute, it should never be moved outside of its parent group.

Required attributes:

id.

Optional attributes:

ctype, ts, clone.

Contents:

Text,
Zero, one or more of the following elements: <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <ph>, <it>, <mrk>, in any order.

<x/>

Generic placeholder - The <x/> element is used to replace any code of the original document. When possible, the ctype allows you to specify what kind of attribute the placeholder represents. A list of preferred values for the ctype attribute is available.

Required attributes:

id.

Optional attributes:

ctype, ts, clone.

Contents:

Empty.

<bx/>

Begin paired placeholder - The <bx/> element is used to replace a beginning paired code of the original document. It should be used for paired codes that do not follow XML well-formedness rules (i.e. no overlapping elements). If the paired codes follow that rule, it is strongly recommended that the <g> element is used because it simplifies processing. The <bx/> element should be followed by a matching <ex/> element. These paired elements are related via their rid attributes. When possible, the ctype allows you to specify what kind of attribute the placeholder represents. A list of preferred values for the ctype attribute is available.

Required attributes:

id.

Optional attributes:

rid, ctype, ts, clone.

Contents:

Empty.

<ex/>

End paired placeholder - The <ex/> element is used to replace a beginning paired code of the original document. It should be used for paired codes that do not follow XML well-formness rules ( i.e. no overlapping elements). If the paired codes follow that rule, it is strongly recommended that the <g> element is used because it simplifies processing. The <ex/> element should be preceded by a matching <bx/> element. These paired elements are related via their rid attributes.

Required attributes:

id.

Optional attributes:

rid, ts.

Contents:

Empty.

<ph>

Placeholder - The <ph> element is used to delimit a sequence of native stand-alone codes in the segment. When possible, the ctype allows you to specify what kind of attribute the placeholder represents. A list of preferred values for the ctype attribute is available.

Required attributes:

id.

Optional attributes:

ctype, ts, crc, assoc. 

Contents:

Code data,
Zero, one or more <sub> elements.

<bpt>

Begin paired tag - The <bpt> element is used to delimit the beginning of a paired sequence of native codes. Each <bpt> has a corresponding <ept> element within the segment. When possible, the ctype allows you to specify what kind of attribute the placeholder represents. A list of preferred values for the ctype attribute is available.

Required attributes:

id.

Optional attributes:

rid, ctype, ts, crc.

Contents:

Code data,
Zero, one or more <sub> elements.

<ept>

End paired tag - The <ept> element is used to delimit the end of a paired sequence of native codes. Each <ept> has a corresponding <bpt> element within the segment.

Required attributes:

id.

Optional attributes:

rid, ts, crc.

Contents:

Code data,
Zero, one or more <sub> elements.

<it>

Isolated tag - The <it> element is used to delimit a beginning/ending sequence of native codes that does not have its corresponding ending/beginning within the segment. When possible, the ctype allows you to specify what kind of attribute the placeholder represents. A list of preferred values for the ctype attribute is available.

Required attributes:

id, pos.

Optional attributes:

rid, ctype, ts, crc.

Contents:

Code data,
Zero, one or more <sub> elements.

<sub>

Sub-flow - The <sub> element is used to delimit sub-flow text inside a sequence of native code, for example: the definition of a footnote or the text of a title attribute in a HTML <a> element. When possible, the ctype allows you to specify what kind of attribute the placeholder represents. Lists of preferred values for the ctype and datatype attributes are available.

Required attributes:

None.

Optional attributes:

datatype, ctype.

Contents:

Text,
Zero, one or more of the following elements: <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <ph>, <it>, <mrk>, in any order.

 

3.2.5. Delimiter Element

XLIFF defines an additional element to support various types of text processing. This element is usually not generated by the extraction module and are ignored most of the time during merging, but it can be very powerful with tools such as Machine Translation, glossary handling, quality assurance, etc.

<mrk>

Marker - The <mrk> element delimits a section of text that has special meaning, such as a terminological unit, a proper name, an item that should not be modified, etc. It can be used for various processing tasks. For example, to indicate to a Machine Translation tool proper names that should not be translated; for terminology verification, to mark suspect expressions after a grammar checking. The <mrk> element is usually not generated by the extraction tool and it is not part of the tags used to merge the XLIFF file back into its original format. A list of preferred values for the mtype attribute is available.

Required attributes:

mtype.

Optional attributes:

mid, ts, comment.

Contents:

Text,
Zero, one or more of the following elements: <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <ph>, <it>, <mrk>, in any order.

 

3.3. Attributes

This section lists the various attributes used in the XLIFF elements. An attribute is never specified more than once for each element. Along with some of the attributes are the "Recommended Attribute Values". Values for these attributes are case sensitive. These lists are purely informative, the goal is to specify a preferred syntax so tools can have some level of compatibility.

XLIFF attributes approved, assoc, attribute, build-num, ctype, category, charclass, comment, company-name, contact-email, contact-name, contact-phone, coord, count-type, crc, css-style, datatype, date, edit, element, exstyle, extradata, extype, font, form, from, help-id, href, id, job-id, match-mandatory, match-quality, maxheight, maxbytes, maxwidth, menu, menu-name, menu-option, mid, mime-type, minheight, minbytes, minwidth, mtype, name, original, phase-name, pos, priority, process-name, product-name, product-version, prop-type, purpose, reformat, resname, restype, rid, source-language, state, style, tool, tool-company, tool-id, tool-name, tool-version, target-language, translate, ts, uid, unit, version.
XML namespace attributes xml:lang, xml:space.

3.3.1. XLIFF Attributes

approved

Approved - Indicates whether a translation is final.

Value description:

Boolean: yes or no.

Default value:

no.

Used in:

<trans-unit>, <bin-unit>.

assoc

Association - Indicates the association of a <ph> with the text prior or after.

Value description:

preceding (the element is associated with the text preceding the element), following (the element is associated with the text following the element), and both (the element is associated with the text on both sides).

Default value:

Undefined.

Used in:

<ph>.

attribute

Attribute - Indicates the attribute name which should or should not be reformatted.

Value description:

Name of the attribute to be or not to be reformatted.

Default value:

Empty string.

Used in:

<reformat>.

build-num

Build number - The build number of version of the product or application the localizable material is for.

Value description:

Alpha-numeric.

Default value:

Undefined.

Used in:

<file>.

category

Category - This would give information on the subject of what is being translated.

Value description:

Text.

Default value:

Undefined.

Used in:

<file>.

charclass

Character class - This indicates that a translation is restricted to a subset of characters (e.g. ASCII only, Katakana only, uppercase only, etc.). A blank value indicates there is no limitation.

Value description:

Text.

Default value:

Undefined.

Used in:

<trans-unit>.

clone

Clone - This indicates that a copy of the given inline element can be made and placed in the <target>.

Value description:

Boolean: yes or no.

Default value:

yes.

Used in:

<g>, <x/>, <bx/>.

comment

Comment - A comment in a tag.

Value description:

Alpha-numeric.

Default value:

Undefined.

Used in:

<mrk>.

company-name

Company name - The client name.

Value description:

Text.

Default value:

Undefined.

Used in:

<phase>.

contact-email

Contact email - The contact email at the client company (email of the contact-name person).

Value description:

Text.

Default value:

Undefined.

Used in:

<phase>.

contact-name

Contact name - The contact at the client company.

Value description:

Text.

Default value:

Undefined.

Used in:

<phase>.

contact-phone

Contact phone - Phone number of the contact-name person.

Value description:

Text.

Default value:

Undefined.

Used in:

<phase>.

context-type

Context type - The context-type attribute specifies the context and the type of resource or style of the data of a given element. For example, to define if it is a label, or a menu item in the case of resource-type data, or the style in the case of document-related data.

Value description:

The base type of the attribute value is xsd:string. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

Pattern: x-[a-z]
Database ??? {To be defined (and all lowercased)}
Element ??? {To be defined (and all lowercased)}
ElementTitle ??? {To be defined (and all lowercased)}
RecordTitle ??? {To be defined (and all lowercased)}
Source file (Proposed only) John Reid: ??? Novell-specific.
Line number (Proposed only) John Reid: ??? Novell-specific.
Num params (Proposed only) John Reid: ??? Novell-specific.
Params notes (Proposed only) John Reid: ??? Novell-specific.
Length preceded (Proposed only) John Reid: ??? Novell-specific.
Internal only (Proposed only) John Reid: ??? Novell-specific.
locale specific (Proposed only) John Reid: ??? Novell-specific.

Default value:

Undefined.

Used in:

<context>.

coord

Coordinates - The coord attribute specifies the x, y, cx and cy coordinates of the text for a given element. The cx and cy values must represent the width and the height (like in Windows resources). The extraction and merging tools must make the right conversion if the original format uses a top-left/bottom-right coordinate system.

Value description:

Four decimal (possibly negative) values, in the order: x,y,cx and cy, separated by semi-colons. Null values may be entered as "#"; (e.g. coord="#;#;183;272").

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <target>, <alt-trans>.

count-type

Count type - The count-type attribute specifies the purpose of the <count> element.

Value description:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

new Indicates the counted units are new. For example, translation units that were not in a previous version of the document.
exact-match Indicates the counted units are exact matches. An extact match occurs when a source text of a segment is exactly the same as the source text of a segment that was translated previously.
fuzzy-match Indicates the counted units are fuzzy matches. A fuzzy match occurs when a source text of a segment is very similar to the source text of a segment that was translated previously (e.g. when the difference is casing, a few changed words, whitesapces discripency, etc.).
total Indicates a total count.
CString (Proposed only) John Reid: ??? Novell-specific.
MsgLib (Proposed only) John Reid: ??? Novell-specific.
needs-translation (Proposed only) Enda McDonnell: Need to be translated.
needs-review (Proposed only) Enda McDonnell: Need to be reviewed.
signed-off (Proposed only) Enda McDonnell: ??? All steps of the translation process are done.
idBasedMatch (Proposed only) Christian Lieske: ??? Indicates the count units are matches based on ID matches (rather than text matches).
noMatch (Proposed only) Christian Lieske: ??? Indicates the count units are translation units without matches.
repetition (Proposed only) Christian Lieske: ??? Indicates the count units are translation units existing already in the same document.
noOfUsages (Proposed only) Christian Lieske: ??? Indicates the count units are items that are used X times in a certain context; example: this is a reusable text unit which is used 42 times in other texts'

Default value:

None.

Used in:

<count>.

crc

Cyclic redundancy checking - A private value used to verify data as it is returned to the producer. The generation and verification of this number is tool-specific.

Value description:

Number (possibly not decimal).

Default value:

None.

Used in:

<internal-file>, <external-file>, <context-group>, <context>, <alt-trans>, <bpt>, <ept>, <it>, <ph>.

css-style

Cascading style-sheet style - The css-style attribute allows any valid CSS style statement to be specified.

Value description:

Text, the value is subject to CSS syntax rules.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <target>, <alt-trans>.

ctype

Content type - The type attribute specifies the content and the type of resource or style of the data of a given element. For example, to define if it is a label, or a menu item in the case of resource-type data, or the style in the case of document-related data.

Value description:

Values for for the ctype attribute of the <x/> and <ph> elements:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

image Indicates a inline image.
pb Indicates a page break.
lb Indicates a line break.

Value for the ctype attribute of the other elements:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

bold Indicates a run of bolded text.
italic Indicates a run of text in italics.
underlined Indicates a run of underlined text.
link Indicates a run of hyper-text.

Default value:

Undefined.

Used in:

<g>, <x/>, <bx/>, <bpt>, <sub>, <it>, <ph>.

datatype

Data type - The datatype attribute specifies the kind of text contained in the element. Depending on that type, you may apply different processes to the data.

Value description:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

javaClass Java source file (extension '.java').
javaPropertyResourceBundle (Proposed only) Christian Lieske: Java property resource bundle
javaListResourceBundle (Proposed only) Christian Lieske: Java list resource bundle
javascript JavaScript source file
jscript (Proposed only) Yves Savourel: JScript source file
cpp C++ source file
c C source file
csharp (Proposed only) Enda McDonnell: C-Sharp
html HyperText Markup Language (HTML) - document instance
xhtml (Proposed only) Christian Lieske: Extensible HyperText Markup Language (XHTML) - document instance
sgml Standard Generalized Markup Language (SGML) - document instance
xml Extensible Markup Language (XML) - document instance
xsl (Proposed only) John Reid: Extensible Stylesheet Language (XSL)
svg (Proposed only) Bryan Schnabel: Scalable Vector Graphic (SVG)
xmlDtd (Proposed only) John Reid: >Extensible Markup Language (XML) - Document Type Definition (DTD)
sgmlDtd (Proposed only) John Reid: Standard Generalized Markup Language (SGML) - Document Type Definition (DTD)
___XML_Schema_datatypes___ (Proposed only) Christian Lieske:
Note: Built-in datatypes from XML schema (see http://www.w3.org/TR/xmlschema-2/#built-in-datatypes for more information) We currently have values like 'datetime'. The portion of the definition for XML schema referred to here includes additional ones (such a 'gYear'). This enables statements such as: 'The stretch of text "12" does designate a year.'
databaseTable (Proposed only) Christian Lieske: Database table
cdf Channel Definition Format (CDF)
interleaf Interleaf
lisp LISP source file
mif Maker Interchange Format (MIF)
pascal Pascal source file
plaintext Plain text file (no formatting other than, possibly, wrapping).
rtf Rich Text Format (RTF)
Note: The 'rtf' accronym may also be used by one of XSLT constructs (this is probably not an issue).
vbscript VisualBasic Script source file
winres Windows resources (i.e. resources extracted from an RC script, a message file, or a compiled file)
resx (Proposed only) Yves Savourel: Windows .NET Resources
mimetype (Proposed only) Gérard Cattin de Bois and Christian Lieske: Indicates that the datatype attribute value is a MIME Type value and is defined in the mime-type attribute (attribute to be defined).
CString (Proposed only) John Reid: ??? Novell-specific.
MsgLib (Proposed only) John Reid: ??? Novell-specific.
po (Proposed only) Enda McDonnell: GNU Portable Object file.
mo (Proposed only) Enda McDonnell: GNU Machine Object file.
csv (Proposed only) Enda McDonnell: Comma-separated values file.
ini (Proposed only) Enda McDonnell: Windows INI file.
resources (Proposed only) Enda McDonnell: Windows .NET binary resources.
messageFile (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
form (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
window (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
menu (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
parameters (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
stringTable (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
report (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
header (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
layout (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
margin (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
footer (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
seedData (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
database (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
dataLoadingFormat (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
HTMLBody (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
javaList (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
warning (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
fileDialog (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
toolbar (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
rts (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
win32-dialog (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
dlgInit (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
RCData (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
XML (Proposed only) Matt Lovatt and Tony Jewtushenko: ???

Default value:

Empty string.

Used in:

<file>, <group>, <trans-unit>, <alt-trans>, <sub>.

date

Date - The date attribute indicates when a given element was created or modified.

Value description:

Date in [ISO 8601] Format. The recommended pattern to use is: CCYY-MM-DDThh:mm:ssZ 
Where: CCYY is the year (4 digits), MM is the month (2 digits), DD is the day (2 digits), hh is the hours (2 digits), mm is the minutes (2 digits), ss is the second (2 digits), and Z indicates the time is UTC time. For example:

date="2002-01-25T21:06:00Z"
is January 25, 2002 at 9:06pm GMT
is January 25, 2002 at 2:06pm US Mountain Time
is January 26, 2002 at 6:06am Japan time

Default value:

Undefined.

Used in:

<file>, <phase>.

edit

Edit - Indicates whether a given attribute or element should or should not be reformatted.

Value description:

Boolean: yes or no.

Default value:

yes.

Used in:

<reformat>.

element

Attribute - Indicates the element name which should or should not be reformatted.

Value description:

Name of the element to be or not to be reformatted.

Default value:

Empty string.

Used in:

<reformat>.

exstyle

Extended style - The exstyle attribute stores the extended style of a control. For example, in Windows resources it corresponds to the EXSTYLE statement.

Value description:

Text.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <target>, <alt-trans>.

extradata

Extra data - The extradata attribute stores the extra data properties of an item.

Value description:

Text.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <alt-trans>.

extype

Extended type - The extype attribute stores the extra type properties of an item.

Value description:

Text.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <alt-trans>.

font

Font - The font attribute specifies the font name, size, and weight of the text for a given element. The font attribute would generally be used for resource-type data: change of font in document-type data can be marked with the <g> element.

Value description:

Name of the font and its size, weight separated by a semi-colon.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <target>, <alt-trans>.

form

Format - Describes the type of format used in an <internal-file> element.

Value description:

The value can be either text (for plain text data), base64 (for data coded in base64 format), or one of values available from the [RFC 1341] document: the MIME specification.

Default value:

text.

Used in:

<internal-file>.

from

From - Indicates the author of a <note> element.

Value description:

Text.

Default value:

Undefined.

Used in:

<note>.

help-id

Help ID - The help-id attribute stores the help identifier of an item. For example, in Windows resources it corresponds to the Help ID parameter of a control.

Value description:

Number.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <alt-trans>.

href

Hypertext reference - The location of the file or the URL for an <external-file> element.

Value description:

Text.

Default value:

Undefined.

Used in:

<external-file>.

id

Identifier - The id attribute is used in many elements, as a unique reference to the original corresponding code data or format for the given element. the id element is not the identifier of a resource: use resname for that purpose.

Value description:

Alpha-numeric without spaces.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <bin-unit>, <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <it>, <ph>.

job-id

Job ID - The identifier given to the localization job.

Value description:

Text.

Default value:

Undefined.

Used in:

<phase>.

match-mandatory

Match mandatory - Indicates that any <alt-trans> element of the parent <trans-unit> must have the same <context> as the <trans-unit>.

Value description:

Boolean: yes or no.

Default value:

no.

Used in:

<context>.

match-quality

Match quality - The match quality of the <alt-trans> element. This value is tool specific and can be a score expressed in percentage or an arbitrary value (e.g. match-quality="high").

Value description:

Text.

Default value:

Undefined.

Used in:

<alt-trans>.

maxheight

Maximum height - The maximum height for the <target> of a <trans-unit>. This could be interpreted as lines, pixels, or any other relevant unit. The unit is determined by the size-unit attribute, which defaults to pixel.

Value description:

Number.

Default value:

Undefined.

Used in:

<trans-unit>.

maxbytes

Maximum bytes - The maximum number of bytes for the <target> of a <trans-unit>. The verification of whether the relevant text respects this requirement must be done using the encoding and line-break type of the final target environment.

Value description:

Number.

Default value:

Undefined.

Used in:

<trans-unit>.

maxwidth

Maximum width - The maximum width for the <target> of a <trans-unit>. This could be interpreted as lines, pixels, or any other relevant unit. The unit is determined by the size-unit attribute, which defaults to pixel.

Value description:

Number.

Default value:

Undefined.

Used in:

<trans-unit>.

menu

Menu - The menu attribute stores the menu property of an item.

Text.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <alt-trans>.

menu-name

Menu name - The menu-name attribute stores the menu name of a control.

Value description:

Text.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <alt-trans>.

menu-option

Menu option - The menu-option attribute stores the option data of a control.

Value description:

Text.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <alt-trans>.

mid

Marker ID - Identifier for an <mrk> element.

Value description:

Text.

Default value:

Undefined.

Used in:

<mrk>.

mime-type

Mime type - Indicates the type of a binary object. This is important in determining how to edit the binary object.

Value description:

Text. A list of preferred values is available from the [RFC 1341] document: the MIME specification.

Default value:

Undefined.

Used in:

<bin-unit>, <bin-target>.

minheight

Minimum height - The minimum height for the <target> of a <trans-unit>. This could be interpreted as lines, pixels, or any other relevant unit. The unit is determined by the size-unit attribute, which defaults to pixel.

Value description:

Number.

Default value:

Undefined.

Used in:

<trans-unit>.

minbytes

Minimum bytes - The minimum number of bytes for the <target> of a <trans-unit>. The verification of whether the relevant text respects this requirement must be done using the encoding and line-break type of the final target environment.

Value description:

Number.

Default value:

Undefined.

Used in:

<trans-unit>.

minwidth

Minimum width - The minimum width for the <target> of a <trans-unit>. This could be interpreted as lines, pixels, or any other relevant unit. The unit is determined by the size-unit attribute, which defaults to pixel.

Value description:

Number.

Default value:

Undefined.

Used in:

<trans-unit>.

mtype

Marker type - The mtype attribute specifies what an <mrk> element is defining within the content of a <source> or <target> element.

Value description:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

abbrev Indicates the marked text is an abbreviation.
datetime Indicates the marked text is a date and/or time.
name Indicates the marked text is a name.
phrase Indicates the marked text is a phrase.
protected Indicates the marked text should not be translated.
term Indicates the marked text is a term.
___ISO-12620_Values___ (Proposed only) Christian Lieske:
Note: Values from ISO 12620 (6.3 data categories -> 2.1.1 term type) For example: main entry term, synonym, quasi-synonym, international scientific term, common name, internationalism, full form, abbreviated form of term, abbreviation, short form of term, initialism, acronym, clipped term, variant, transliterated form, transcribed form, romanized form, symbol, formula, equation, logical expression, stock keeping unit, part number, phraseological unit, collocation, set phrase, synonymous phrase, standard text

Default value:

Undefined.

Used in:

<mrk>.

name

Name - The name attribute specifies the user-defined name of a named group element.

Value description:

Text.

Default value:

Undefined.

Used in:

<prop-group>, <context-group>, <count-group>.

origin

Translation Match Origin - The origin attribute specifies where a translation match came from; for example, from a previous version of the same product, a different product, a shared translation memory, etc.

Value description:

Text.

Default value:

Undefined.

Used in:

<alt-trans>.

original

Original file - The original attribute specifies the name of the original file from which the contents of a <file> element has been extracted.

Value description:

Text.

Default value:

Undefined.

Used in:

<file>.

phase-name

Phase Name - The phase-name attribute allows to name uniquely a <phase> element. It is also used in other elements in the file to refer to the given <phase> element.

Value description:

Text.

Default value:

Undefined.

Used in:

<phase>, <trans-unit>, <target>, <bin-unit>, <bin-target>.

pos

Position - Indicates whether an isolated tag <it> is a beginning or and ending tag.

Value description:

open or close.

Default value:

Undefined.

Used in:

<it>.

priority

Priority - The priority of a <note> element.

Value description:

A number between 1 and 10, 1 being the highest priority.

Default value:

1

Used in:

<note>.

process-name

Process name - The name specifying the type of process a given <phase> corresponds (e.g. Translation, Proofreading, Sizing, etc.).

Value description:

Text.

Default value:

Undefined.

Used in:

<phase>.

product-name

Product name - The name of the product which uses this file.

Value description:

Text.

Default value:

Undefined.

Used in:

<file>.

product-version

Product version - The version of the product which uses this file.

Value description:

Alpha-numeric.

Default value:

Undefined.

Used in:

<file>.

prop-type

Property type - The prop-type attribute specifies the type of a <prop> element.

Value description:

Text. No value defined by the standard.

Default value:

Undefined.

Used in:

<prop>.

purpose

Purpose - The purpose attribute specifies the purpose of a <context-group> element.

Value description:

The base type of the attribute value is xsd:string. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

location (Proposed only) Mark Levins: The context-group is used to specify where the term was found in the translatable source. Thus, it is not displayed.
match (Proposed only) Mark Levins/John Reid: Specifies that the context information should be used during translation memory lookups. Thus, it is not displayed.
information (Proposed only) Mark Levins: Specifies that the context is informational in nature, indicating for example, how a term should be translated. Thus, should be displayed to anyone editing the XLIFF.

Combinations of these values can be made via the standard mechanism of XLIFF. Thus, purpose="location;match" would provide both location and TM matching contextual information.

Default value:

Undefined.

Used in:

<context-group>.

reformat

Reformat - Indicates whether the target can be formatted (size, font, etc.) different than the source.

[NOTE: We need to decide what to do with this attribute, if we use <reformat> instead.]

Value description:

Boolean: yes or no.

Default value:

yes.

Used in:

<trans-unit>, <bin-unit>.

resname

Resource name - Resource name or identifier of a item. For example: the key in the key/value pair in a Java properties file, the ID of a string in a Windows string table, the index value of an entry in a database table, etc.

Value description:

Text.

Default value:

Undefined.

Used in:

<group>. <trans-unit>, <alt-trans>, <target>, <bin-unit>, <bin-target>.

restype

Resource type - Indicates the type of the container element.

Value description:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

button Indicates a button object, for example a PUSHBUTTON contol Windows.
caption Indicates a caption, such as the caption of a dialog box.
checkbox Indicates check box object, for example a AUTOCHECKBOX control in Windows.
cell Indicates the cell in a table, for example the content of the <td> element in HTML.
dialog Indicates a dialog box.
file Indicates a filename.
fn Indicates a footnote.
footer Indicates a footer.
font Indicates a font name.
frame Indicates a frame object.
header Indicates a header item.
heading Indicates a heading, such has the content of <h1>, <h2>, etc. in HTML.
keywords Indicates keyword list, such as the content of the Keywords meta-data in HTML, or a K footnote in WinHelp RTF.
label Indicates a label object.
listitem Indicates an list item (an entry in a list).
menu Indicates a menu (a group of menu-items).
menuitem Indicates a menu item (an entry in a menu).
message Indicates a message, for example an entry in a MESSAGETABLE resource in Windows.
radio Indicates a radio button object, for example a RADIOBUTTON control in Windows.
shortcut Windows accelerators, shortcuts in resource or property files.
string Indicates a string, for example an entry in a STRINGTABLE resource in Windows.
var Indicates the text of a variable.
uri (Proposed only) Yves Savourel: Indicates a URI (URN or URL).
bitmap (Proposed only) Yves Savourel: Indicates a bitmap, for example a BITMAP resource in Windows.
icon (Proposed only) Yves Savourel: Indicates an icon, for example a BITMAP resource in Windows.
cursor (Proposed only) Yves Savourel: Indicates a cursor, for example a CURSOR resource in Windows.
edit (Proposed only) Yves Savourel: Indicates an edit box object, for example an EDIT control in Windows.
static (Proposed only) Yves Savourel: Indicates a static object.
combobox (Proposed only) Yves Savourel: Indicates a combination of edit box and listbox object, for example a COMBOBOX control in Windows.
scrollbar (Proposed only) Yves Savourel: Indicates a scrollbar object, for example a SCROLLBAR control in Windows.
listbox (Proposed only) Yves Savourel: Indicates a listbox object, for example an LISTBOX control in Windows.
pushbox (Proposed only) Yves Savourel: Indicates a pushbox object, for example a PUSHBOX control in Windows.
groupbox (Proposed only) Yves Savourel: Indicates a groupbox object, for example a GROUPBOX control in Windows.
accelerator (Proposed only) Yves Savourel: Indicates an accelerator object, for example an entry in an ACCELERATORS resource in Windows.
list (Proposed only) Yves Savourel: Indicates a list (a group of list-items, for example an <ol> or <ul> element in HTML).
___XUL_Objects___ (Proposed only) Christian Lieske:
Note: Values from the object defined in XUL. See http://www.xulplanet.com/references/elemref/ (the set titled "XUL Elements") for the complete list.
linklabel (Proposed only) Enda McDonnell: Indicates a label that is also a HTML link (not necessarily a URL).
panel (Proposed only) Enda McDonnell: Catch all for rectangular areas.
checked-listbox (Proposed only) Enda McDonnell: Indicates a list box, but with a check-box for each item.
treecontrol (Proposed only) Enda McDonnell: Indicates a hierarchical list of items.
tabcontrol (Proposed only) Enda McDonnell: Indicates a layers of controls with a tab to select layers.
datetimepicker (Proposed only) Enda McDonnell: Indicates a date/time picker.
monthcalendar (Proposed only) Enda McDonnell: Indicates a calendar control.
splitter (Proposed only) Enda McDonnell: Indicates a splitter bar.
numericupdown (Proposed only) Enda McDonnell: Indicates an edit box beside a spin control.
trackbar (Proposed only) Enda McDonnell: Indicates a bar with a pointer indicating a position within a certain range.
progressbar (Proposed only) Enda McDonnell: Indicates a vertical or horizontal bar that gets shaded depending on progress.
toolbar (Proposed only) Enda McDonnell: Indicates an array of controls, usually buttons.
tooltip (Proposed only) Enda McDonnell: Indicates a pop up tool tip text.
statusbar (Proposed only) Enda McDonnell: Indicates a window for providing feedback to the users, like 'read-only', etc..
Component (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Container (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
CellRendererPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Button (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
MenuItem (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
CheckBoxMenuItem (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Menu (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
RadioButtonMenuItem (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ToggleButton (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
CheckBox (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
RadioButton (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Box (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ColorChooser (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ComboBox (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
FileChooser (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
InternalFrame (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Label (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
LayeredPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
DesktopPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
List (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
MenuBar (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
OptionPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Panel (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Spinner (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
PopupMenu (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ProgressBar (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
RootPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ScrollBar (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ScrollPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Separator (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
PopupMenu (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
PopupMenu (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ToolBar (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Slider (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
SplitPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
TabbedPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Table (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
TextComponent (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
EditorPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
TextPane (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
TextArea (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
TextField (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
FormattedTextField (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
PasswordField (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ToolBar (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
ToolTip (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Tree (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Viewport (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Dialog (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Dialog (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Frame (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).
Window (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Note: From Java SwingBased (http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/package-tree.html).

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <target>, <alt-trans>, <bin-unit>, <bin-target>.

rid

Reference identifier - The rid attribute is used to link different elements that are related. For example, a reference to its definition, or paragraphs belonging to the same group, etc.

Value description:

Alpha-numeric without spaces.

Default value:

Undefined.

Used in:

<bpt>, <ept>, <it>, <bx/>, <ex/>.

size-unit

Unit of size attributes - The size-unit attribute specifies the units of measure used in the maxheight, minheight, maxwidth, and minwidth attributes.

Value description:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

pixel Pixels.
Note: Enda McDonnell would prefer 'pixels'
byte 8-bit bytes.
Note: Enda McDonnell would prefer 'chars-8bit'
char Unicode characters.
Note: Enda McDonnell would prefer 'chars-16bit'
dlgunit (Proposed only) Yves Savourel: Dialog units, as defined in Windows resources.
Note: Enda McDonnell would prefer 'dlgunits'
rows (Proposed only) Enda McDonnell: The HTML unit for text area.
cols (Proposed only) Enda McDonnell: The HTML unit for text area.
point (Proposed only) Matt Lovatt and Tony Jewtushenko: ??? Point.

Default value:

pixel.

Used in:

<trans-unit>.

source-language

Source language - The language for the <source> elements in the given <file> element.

Value description:

A language code as described in the [RFC 3066]. The values for this attribute follow the same rules as the values for xml:lang. Unlike the other XLIFF attributes, the values for xml:lang are not case-sensitive. For more information see the section on xml:lang in the XML specification, and the erratum E11 (which replaces RFC 1766 by RFC 3066).

The source language can be also specified by xml:lang in each <source> element. The value of source-language and xml:lang can be different to allow having different source languages if necessary (for example in an <alt-trans> element).

Default value:

Undefined.

Used in:

<file>.

state

State - The status of a particular translation in a <target> or <bin-target> element.

Value description:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

needs-translation Indicates the item needs to be translated.
needs-review Indicates the item needs to be reviewed.
needs-resizing Indicates the item needs to be resized.
needs-review-textonly (Proposed only) Enda McDonnell: Only text needs to be reviewed.
needs-review-sizeonly (Proposed only) Enda McDonnell: Only size (coordinates) needs to be reviewed.
signed-off (Proposed only) Enda McDonnell: Indicates a definite reviewed/compleation status.
not-executable (Proposed only) Christian Lieske: ??? Workflow state.
executable (Proposed only) Christian Lieske: ??? Workflow state.
started (Proposed only) Christian Lieske: ??? Workflow state.
suspended (Proposed only) Christian Lieske: ??? Workflow state.
aborted (Proposed only) Christian Lieske: ??? Workflow state.
preliminary-finished (Proposed only) Christian Lieske: ??? Workflow state.
finished (Proposed only) Christian Lieske: ??? Workflow state.
New (Proposed only) Matt Lovatt and Tony Jewtushenko: ??? New.
Candidate (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Leveraged (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Leveraged-Inherited (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Leveraged-Glossary (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Leveraged-Repository (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Leveraged-TM (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Leveraged-MT (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Translated (Proposed only) Matt Lovatt and Tony Jewtushenko: ??? Has been translated.
Repaired (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
Commented (Proposed only) Matt Lovatt and Tony Jewtushenko: ???
ForReview (Proposed only) Matt Lovatt and Tony Jewtushenko: ???

Default value:

Undefined.

Used in:

<target>, <bin-target>.

style

Style - The resource style of a control. For example, in Windows resources it corresponds to the STYLE statement.

Value description:

Text.

Default value:

Undefined.

Used in:

<group>, <trans-unit>, <target>, <alt-trans>.

target-language

Target language - The language for the <target> elements in the given <file> element.

Value description:

A language code as described in the [RFC 3066]. The values for this attribute follow the same rules as the values for xml:lang. Unlike the other XLIFF attributes, the values for xml:lang are not case-sensitive. For more information see the section on xml:lang in the XML specification, and the erratum E11 (which replaces RFC 1766 by RFC 3066).

The target language can be also specified by xml:lang in each <target> element. The value of target-language and xml:lang can be different to allow having different target languages if necessary (for example in an <alt-trans> element).

Default value:

Undefined.

Used in:

<file>.

tool

Creation tool - The tool attribute is used to specify the signature and version of the tool that created or modified the document.

Important: The tool attribute is DEPRECATED in version 1.1. Instead, use the <tool> element and a tool-id attribute.

Value description:

Text

Default value:

manual.

Used in:

<file>, <phase>, <alt-trans>.

tool-company

Tool company - The tool-company attribute allows to specify the company from which a tool originates.

Value description:

Text

Default value:

Undefined.

Used in:

<tool>.

tool-id

Tool identifier - The tool-id attribute allows to identify uniquely a <tool> element. It is also used in other elements in the file to refer to the given <tool> element.

Value description:

Text

Default value:

Undefined.

Used in:

<file>, <phase>, <alt-trans>, <tool>.

tool-name

Tool name - The tool-name attribute allows to specify the name of a given tool.

Value description:

Text

Default value:

Undefined.

Used in:

<tool>.

tool-version

Tool version - The tool-version attribute allows to specify the version of a given tool.

Value description:

Text

Default value:

Undefined.

Used in:

<tool>.

translate

Translate - Indicates whether or not the text referred to should be translated.

Value description:

Boolean: yes or no.

Default value:

yes.

Used in:

<trans-unit>, <bin-unit>.

ts

Tool-specific data - The ts attribute allows you to include short data understood by a specific toolset. You can also use the <prop> element to define large properties at the element level.

Important: The ts attribute is DEPRECATED in version 1.1. Instead, use attributes defined in a namespace different from XLIFF. See the Extensibility section for more information.

Value description:

Text. No value defined by the standard.

Default value:

Undefined.

Used in:

<file>, <group>, <trans-unit>, <source>, <target>, <bin-unit>, <bin-source>, <bin-target>, <alt-trans>, <mrk>, <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <ph>, <it>.

uid

Unique ID - The unique id used to identify the skeleton file.

Value description:

Text.

Default value:

Undefined.

Used in:

<external-file>.

unit

Unit - The units counted in a <count> element.

Value description:

The base type of the attribute value is xsd:NMTOKEN. The pre-defined values are defined in the table below. If user-defined values are used, they must start with a "x-" prefix.

word Refers to words.
page Refers to pages.
trans-unit Refers to <trans-unit> elements.
bin-unit Refers to <bin-unit> elements.
item Indicates <trans-unit> and/or <bin-unit> elements.
character (Proposed only) Christian Lieske: Refers to characters.
line (Proposed only) Christian Lieske: Refers to lines.
sentence (Proposed only) Christian Lieske: Refers to sentences.
paragraph (Proposed only) Christian Lieske: Refers to paragraphs.
segment (Proposed only) Christian Lieske: Referes to segments.
placeable (Proposed only) Christian Lieske: ??? Referes to placeables.

Default value:

Undefined.

Used in:

<count>.

version

XLIFF version - The version attribute is used to specify the format version of the XLIFF document.

Value description:

Fixed text.

Default value:

1.1

Used in:

<xliff>.

 

3.3.2. XML Namespace Attributes

xml:lang

Language - The xml:lang attribute specifies the language variant of the text of a given element.

Value description:

A language code as described in the [RFC 3066]. This declared value is considered to apply to all elements within the content of the element where it is specified, unless overridden with another instance of the xml:lang attribute. Unlike the other XLIFF attributes, the values for xml:lang are not case-sensitive. For more information see the section on xml:lang in the XML specification, and the erratum E11 (which replaces RFC 1766 by RFC 3066).

Default value:

Undefined.

Used in:

<xliff>, <note>, <prop>, <source>, <target>, <alt-trans>.

xml:space

White spaces - The xml:space attribute specifies how white spaces (ASCII spaces, tabs and line-breaks) should be treated.

Value description:

default or preserve. The value default signals that applications' default white-space processing modes are acceptable for this element; the value preserve indicates the intent that applications preserve all the white space. This declared intent is considered to apply to all elements within the content of the element where it is specified, unless overridden with another instance of the xml:space attribute.

For more information see the section on xml:space in the XML specification.

Default value:

default.

Used in:

<file>, <group>, <trans-unit>, <alt-trans>.

 

A. XLIFF Tree Structure

The following figure shows the possible structure as a tree. Each element is followed by notation indicating its possible occurrence according to the corresponding legend.

[NOTE: The tree has been completely redone. Please double check it.]

(legend: 1 = one
         + = one or more
         ? = zero or one
         * = zero, one or more)

<xliff>1
|
+--- <file>+
     |
     +--- <header>?
     |    |
     |    +--- <skl>?
     |    |    |
     |    |    +--- (<internal-file> | <external-file>)1
     |    |
     |    +--- <phase-group>?
     |    |    |
     |    |    +--- <phase>+
     |    |         |
     |    |         +--- <note>*
     |    |
     |    +--- <glossary>*
     |    |    |
     |    |    +--- (<internal-file> | <external-file>)1
     |    |
     |    +--- <reference>*
     |    |    |
     |    |    +--- (<internal-file> | <external-file>)1
     |    |
     |    +--- <count-group>*
     |    |    |
     |    |    +--- <count>*
     |    |
     |    +--- <tool>*
     |    |    |
     |    |    +--- [Extension Point]
     |    |
     |    +--- <prop-group>*
     |    |    |
     |    |    +--- <prop>*
     |    |
     |    +--- [Extension Point]
     |    |
     |    +--- <note>*
     |
     +--- <body>1
          |
          +--- <group>*
          |    |
          |    +--- <context-group>*
          |    |    |
          |    |    +--- <context>+
          |    |
          |    +--- <count-group>*
          |    |    |
          |    |    +--- <count>*
          |    |
          |    +--- <prop-group>*
          |    |    |
          |    |    +--- <prop>*
          |    |
          |    +--- [Extension Point]
          |    |
          |    +--- <note>*
          |    |
          |    +--- At least one of: (<group>* <trans-unit>* <bin-unit>*)
          |
          +--- <trans-unit>*
          |    |
          |    +--- <source>1
          |    |    |
          |    |    +--- [Inline Elements]
          |    |
          |    +--- <target>?
          |    |    |
          |    |    +--- [Inline Elements]
          |    |
          |    +--- <context-group>*
          |    |    |
          |    |    +--- <context>+
          |    |
          |    +--- <count-group>*
          |    |    |
          |    |    +--- <count>*
          |    |
          |    +--- <prop-group>*
          |    |    |
          |    |    +--- <prop>*
          |    |
          |    +--- [Extension Point]
          |    |
          |    +--- <note>*
          |    |
          |    +--- <alt-trans>*
          |         |
          |         +--- <context-group>*
          |         |    |
          |         |    +--- <context>+
          |         |
          |         +--- <source>?
          |         |    |
          |         |    +--- [Inline Elements]
          |         |
          |         +--- <target>+
          |         |    |
          |         |    +--- [Inline Elements]
          |         |
          |         +--- <prop-group>*
          |         |    |
          |         |    +--- <prop>*
          |         |
          |         +--- [Extension Point]
          |         |
          |         +---- <note>*
          |
          +--- <bin-unit>*
               |
               +--- <bin-source>1 & <bin-target>?
               |    |
               |    +--- (<internal-file> | <external-file>)1
               |
               +--- <context-group>*
               |    |
               |    +--- <context>+
               |
               +--- <count-group>*
               |    |
               |    +--- <count>*
               |
               +--- <prop-group>*
               |    |
               |    +--- <prop>*
               |
               +--- [Extension Point]
               |
               +--- <note>*
               |
               +--- <trans-unit>*



Inline Elements:

---+--- <ph>*
   |    |
   |    +--- <sub>*
   |         |
   |         +--- [Inline Elements]
   |
   +--- <it>*
   |    |
   |    +--- <sub>*
   |         |
   |         +--- [Inline Elements]
   |
   +--- <bpt>*
   |    |
   |    +--- <sub>*
   |         |
   |         +--- [Inline Elements]
   |
   +--- <ept>*
   |    |
   |    +--- <sub>*
   |         |
   |         +--- [Inline Elements]
   |
   +--- <x/>*
   |    |
   |    +--- [Inline Elements]
   |
   +--- <bx/>*
   |    |
   |    +--- [Inline Elements]
   |
   +--- <ex/>*
   |    |
   |    +--- [Inline Elements]
   |
   +--- <mrk>*
        |
        +--- [Inline Elements]

B. Document Type Definition and Schemas

C. Changes Since Previous Version (Non-Normative)

The changes in this version relative to the previous version are as follows:

[This is the list of the changes made in this document from v1.0. Need to be cleaned up to keep only changes that affect the format itself.]

D. Naming Guidelines (Non-Normative)

The following naming guidelines were used in writing this specification.

D.1. Elements and Attributes

The following guidelines were used for element and attribute naming.

  1. Standard English letters.
  2. Lower case only.
  3. Hyphen is the preferred mean for creating composite names.
  4. Industry standard terminology should be followed where possible.

D.2. Attribute Values

Attribute values are case sensitive. It is strongly recommended that lower-case values are used. The specification recommends a number of values for some attributes, these are all lower-case.

Where multiple attribute values are to be used in an XLIFF document, two approaches are used: For enumerated attributes (such as the purpose attribute of <context-group>) the separator must be a space. For other textual attributes based on string, the specification recommends the use of the semi-colon as a separator for values. For example, multiple contacts may be listed for a <file> with the attribute written thusly: contact-name="Frank Sinatra;Sammy Davis Jnr;Dean Martin".

D.3. Processing Instructions

XLIFF reserves processing instructions that begin with "xliff-".

D.4. XLIFF File Extension

XLIFF documents use the .xlf extension. No other extension is recommended by the specification.

E. XLIFF Technical Committee (Non-Normative)

The XLIFF Technical Committee at OASIS is composed of the following members:

[Need to get the latest updated list]

E. References

Normative

[IANA Charsets]
IANA Names for Character Sets. IANA (Internet Assigned Numbers Authority), Aug 2001
[ISO 639]
Codes for the Representation of Names of Languages. ISO (International Standards Organization), Nov 2001.
[ISO 3166]
Codes for the representation of names of countries and their subdivisions. ISO (International Organization for Standardization), Jun 2000.
[ISO 8601]
Representation of dates and times. ISO (International Organization for Standardization), Dec 2000.
[OpenTag 1.2]
OpenTag Format Specifications. ILE (International Language Engineering), Nov 1998.
[RFC 1341]
Multipurpose Internet Mail Extensions. IETF (Internet Engineering Task Force), Jun 1992.
[RFC 3066]
RFC 3066 Tags for the Identification of Languages. IETF (Internet Engineering Task Force), Jan 2001.
[TMX 1.3]
TMX Format Specifications. LISA (Localisation Industry Standards association), Aug 2001.
[XML 1.0]
Extensible Markup Language (XML) 1.0 Second Edition. W3C (World Wide Web Consortium), Oct 2000.
[XML Names]
Namespaces in XML. W3C (World Wide Web Consortium), Jan 1999.

Non-Normative

[ISO]
International Organization for Standardization Web site.
[LISA]
Localisation Industry Standards Association Web site.
[OASIS]
Organization for the Advancement of Structured Information Standards Web site.
[Unicode]
Unicode Consortium Web site.
[W3C]
World Wide Web Consortium Web site.