This document defines version 2.0 of the XML Localisation 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 and among tools.
XLIFF (Format de fichier XML pour l'échange de données de localisation)
XLIFF (format XML datoteke za izmenjavo lokalizacije)
Ta dokument opredeljuje različico 2.0 formata XML datoteke za izmenjavo lokalizacije (XLIFF). Namen tega slovarja je shraniti podatke, ki jih je mogoče lokalizirati, in jih prenesti iz enega koraka postopka lokalizacije v drugega, hkrati pa omogočiti interoperabilnost med orodji.
ISO 21720:2024 specifies the XLIFF (XML Localization Interchange File Format) family for exchanging localizable content between tools and processes. Published as the second edition of ISO 21720, this document standardizes XLIFF 2.x behaviour to enable interoperability, lossless interchange of source and translated text, and modular extension for real-world localization workflows. The edition documents major updates (notably features introduced in XLIFF 2.1) such as advanced validation and native support for ITS 2.0 while also tightening schema-level constraints for language attributes.
Key Topics and Technical Requirements
Core specification: minimal XML elements and attributes required to extract, carry and merge localized content. The core uses the namespace urn:oasis:names:tc:xliff:document:2.0.
Conformance and processing rules: definitions for Agents (Extractor, Enricher, Writer, Merger), processing operations (Extraction, Enriching, Modification, Merging) and normative interpretation of requirement keywords (RFC 2119).
Fragment identification & selectors: mechanisms to reference parts of documents for fine-grained processing and merging.
Inline content and segmentation: rules for inline codes, annotations, sub-flows, bidirectional text and segment representation/order.
Modules and extensions: optional modules with separate namespaces and schemas, including Translation Candidates, Glossary, Format Style, Metadata, Resource Data, Size & Length, Validation and the ITS Module (integration with ITS 2.0). Change Tracking is defined as an extension.
Validation artifacts & schemas: machine-readable schemas and validation guidance; the core XSD enforces xs:language on srcLang/trgLang and restores xml:lang constraints for .
Security/privacy considerations: media type registration and guidance for potentially sensitive constructs (see appendices).
Normative references: BCP 47, RFCs for media types and IRIs, HTML5, Schematron and related ISO documents.
Applications and Who Uses It
Localization service providers and translators: for receiving and returning translated segments with context and inline markup preserved.
CAT tool and TMS developers: to implement imports/exports, translation memory integration and validation against XLIFF schemas.
Software and content producers (publishers, product teams): to extract UI strings, documentation and web content for localization, then merge translations back.
Automation and CI/CD localization pipelines: to enable tool-agnostic exchange of multilingual assets and validate translations during builds.
Benefits include standardized interchange, reduced manual rework, reliable round-trip merging, and compatible integration with ITS metadata for internationalization.
Related Standards
ITS 2.0 (W3C Internationalization Tag Set) - native support integrated via the ITS Module
ISO 21720:2024 is a standard published by the International Organization for Standardization (ISO). Its full title is "XLIFF (XML Localization Interchange File Format)". This standard covers: This document defines version 2.0 of the XML Localisation 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 and among tools.
This document defines version 2.0 of the XML Localisation 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 and among tools.
ISO 21720:2024 is classified under the following ICS (International Classification for Standards) categories: 35.240.30 - IT applications in information, documentation and publishing. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO 21720:2024 has the following relationships with other standards: It is inter standard links to ISO 21720:2017. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
You can purchase ISO 21720:2024 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of ISO standards.
SLOVENSKI STANDARD
01-november-2024
XLIFF (format XML datoteke za izmenjavo lokalizacije)
XLIFF (XML Localization Interchange File Format)
XLIFF (Format de fichier XML pour l'échange de données de localisation)
Ta slovenski standard je istoveten z: ISO 21720:2024
ICS:
35.240.30 Uporabniške rešitve IT v IT applications in information,
informatiki, dokumentiranju in documentation and
založništvu publishing
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
You can have the following fragment identifiers:
• #f=f1/u=u1/1 refers to the element of the source content of
the element .
• #f=f1/u=u1/t=1 refers to the element of the target content of
.
the element
• #f=f1/n=n1 refers to the element of the element
id="f1">.
• #f=f1/u=u1/n=n1 refers to the element of the element
.
• #f=f1/u=u1/s1 refers to the element of the element
.
• Assuming the extension defined by the namespace URI myNamespaceURI has
registered the prefix myprefix, the expression #f=f1/u=u1/myprefix=x1
of the element
refers to the element
id="u1">.
4 The Core Specification
XLIFF is a bilingual document format designed for containing text that needs
Translation, its corresponding translations and auxiliary data that makes the
Translation process possible.
At creation time, an XLIFF Document MAY contain only text in the source language.
Translations expressed in the target language MAY be added at a later time.
The root element of an XLIFF Document is . It contains a collection of
elements. Typically, each element contains a set of elements
that contain the text to be translated in the child of one or more
elements. Translations are stored in the child of each element.
4.1 General Processing Requirements
• An Agent processing a valid XLIFF Document that contains XLIFF-defined
elements and attributes that it cannot handle MUST preserve those elements
and attributes.
• An Agent processing a valid XLIFF Document that contains custom elements
and attributes that it cannot handle SHOULD preserve those elements and
attributes.
4.2 Elements
This section contains a description of all elements used in XLIFF Core.
4.2.1 Tree Structure
Legend:
1 = one
+ = one or more
? = zero or one
* = zero or more
4.2.2 Structural Elements
The structural elements used in XLIFF Core are: , , ,
, , , , , , ,
, and .
4.2.2.1 xliff
Root element for XLIFF documents.
Contains:
- One or more elements
Attributes:
- version, REQUIRED
- srcLang, REQUIRED
- trgLang, OPTIONAL
- xml:space, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The trgLang attribute is REQUIRED if and only if the XLIFF Document
contains elements that are children of or .
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- the its:versionattribute from the namespace
http://www.w3.org/2005/11/its, OPTIONAL.
4.2.2.2 file
Container for localization material extracted from an entire single document, or
another high level self contained logical node in a content structure that cannot be
described in the terms of documents.
Note
Sub-document artifacts such as particular sheets, pages, chapters
and similar are better mapped onto the element. The
element is intended for the highest logical level. For instance a
collection of papers would map to a single XLIFF Document, each
paper will be represented with one element, whereas chapters
and subsections will map onto nested elements.
Contains:
- Zero or one element followed by
- elements from other namespaces, OPTIONAL
- Zero or one element followed by
- One or more or elements in any order.
Attributes:
- id, REQUIRED
- canResegment, OPTIONAL
- original, OPTIONAL
- translate, OPTIONAL
- srcDir, OPTIONAL
- trgDir, OPTIONAL
- xml:space, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The following XLIFF Module elements are explicitly allowed by the wildcard
other:
- Zero or one elements
- Zero or one element
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero, one, or more elements
• Module and Extension elements MAY be used in any order.
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- attributes from the namespace urn:oasis:names:tc:xliff:fs:2.0, OPTIONAL,
provided that the Constraints specified in the Format Style Module are met.
- attributes from the namespace
urn:oasis:names:tc:xliff:sizerestriction:2.0, OPTIONAL, provided that
the Constraints specified in the Size and Length Restriction Module are met.
- attributes from the namespace http://www.w3.org/2005/11/its, OPTIONAL,
provided that the Constraints specified in the ITS Module are met.
- attributes from the namespace urn:oasis:names:tc:xliff:itsm:2.1,
OPTIONAL, provided that the Constraints specified in the ITS Module are met.
4.2.2.3 skeleton
Container for non-translatable material pertaining to the parent element.
Contains:
Either
- Non-translatable text
- elements from other namespaces
or
- is empty.
Attributes:
- href, OPTIONAL
Constraints
• The attribute href is REQUIRED if and only if the element is
empty.
Processing Requirements
• Modifiers and Enrichers processing an XLIFF Document that contains a
element MUST NOT change that element, its attributes, or its
content.
• Extractors creating an XLIFF Document with a element MUST
leave the element empty if and only if they specify the attribute
href.
4.2.2.4 group
Provides a way to organize units into a structured hierarchy.
Note that this is especially useful for mirroring a source format's hierarchical
structure.
Contains:
- elements from other namespaces, OPTIONAL
- Zero or one element followed by
- Zero, one or more or elements in any order.
Attributes:
- id, REQUIRED
- name, OPTIONAL
- canResegment, OPTIONAL
- translate, OPTIONAL
- srcDir, OPTIONAL
- trgDir, OPTIONAL
- type, OPTIONAL
- xml:space, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The following XLIFF Module elements are explicitly allowed by the wildcard
other:
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero, one, or more elements
• Module and Extension elements MAY be used in any order.
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- attributes from the namespace urn:oasis:names:tc:xliff:fs:2.0, OPTIONAL,
provided that the Constraints specified in the Format Style Module are met.
- attributes from the namespace
urn:oasis:names:tc:xliff:sizerestriction:2.0, OPTIONAL, provided that
the Constraints specified in the Size and Length Restriction Module are met.
- attributes from the namespace http://www.w3.org/2005/11/its, OPTIONAL,
provided that the Constraints specified in the ITS Module are met.
- attributes from the namespace urn:oasis:names:tc:xliff:itsm:2.1,
OPTIONAL, provided that the Constraints specified in the ITS Module are met.
4.2.2.5 unit
Static container for a dynamic structure of elements holding the extracted
translatable source text, aligned with the Translated text.
Contains:
- elements from other namespaces, OPTIONAL
- Zero or one elements followed by
- Zero or one element followed by
- One or more or elements in any order.
Attributes:
- id, REQUIRED
- name, OPTIONAL
- canResegment, OPTIONAL
- translate, OPTIONAL
- srcDir, OPTIONAL
- trgDir, OPTIONAL
- xml:space, OPTIONAL
- type, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• A MUST contain at least one element.
• The following XLIFF Module elements are explicitly allowed by the wildcard
other:
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero, one, or more elements
- Zero, one, or more elements
• Module and Extension elements MAY be used in any order.
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- attributes from the namespace urn:oasis:names:tc:xliff:fs:2.0, OPTIONAL,
provided that the Constraints specified in the Format Style Module are met.
- attributes from the namespace
urn:oasis:names:tc:xliff:sizerestriction:2.0, OPTIONAL, provided that
the Constraints specified in the Size and Length Restriction Module are met.
- attributes from the namespace http://www.w3.org/2005/11/its, OPTIONAL,
provided that the Constraints specified in the ITS Module are met.
- attributes from the namespace urn:oasis:names:tc:xliff:itsm:2.1,
OPTIONAL, provided that the Constraints specified in the ITS Module are met.
4.2.2.6 segment
This element is a container to hold in its aligned pair of children elements the
minimum portion of translatable source text and its Translation in the given
Segmentation.
Contains:
- One element followed by
- Zero or one element
Attributes:
- id, OPTIONAL
- canResegment, OPTIONAL
- state, OPTIONAL
- subState, OPTIONAL
4.2.2.7 ignorable
Part of the extracted content that is not included in a segment (and therefore not
translatable). For example tools can use to store the white space
and/or codes that are between two segments.
Contains:
- One element followed by
- Zero or one element
Attributes:
- id, OPTIONAL
4.2.2.8 notes
Collection of comments.
Contains:
- One or more elements
4.2.2.9 note
This is an XLIFF specific way how to present end user readable comments and
annotations. A note can contain information about , , ,
, or elements.
Contains:
- Text
Attributes:
- id, OPTIONAL
- appliesTo, OPTIONAL
- category, OPTIONAL
- priority, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- fs:fs, OPTIONAL
- fs:subFs, OPTIONAL
4.2.2.10 originalData
Unit-level collection of original data for the inline codes.
Contains:
- One or more elements
4.2.2.11 data
Storage for the original data of an inline code.
Contains:
- Non-translatable text
- Zero, one or more elements.
Non-translatable text and elements MAY appear in any order.
Attributes:
- id, REQUIRED
- dir, OPTIONAL
- xml:space, OPTIONAL, the value is restricted to preserve on this element
4.2.2.12 source
Portion of text to be translated.
Contains:
- Text
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
Text and inline elements may appear in any order.
Attributes:
- xml:lang, OPTIONAL
- xml:space, OPTIONAL
Constraints
• When a element is a child of or , the
explicit or inherited value of the OPTIONAL xml:lang attribute MUST be
equal to the value of the srcLang attribute of the enclosing element.
4.2.2.13 target
The translation of the sibling element.
Contains:
- Text
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
Text and inline elements may appear in any order.
Attributes:
- xml:lang, OPTIONAL
- xml:space, OPTIONAL
- order, OPTIONAL
Constraints
• When a element is a child of or , the
explicit or inherited value of the OPTIONAL xml:lang MUST be equal to the
value of the trgLang attribute of the enclosing element.
4.2.3 Inline Elements
The XLIFF Core inline elements at the or level are: , ,
, , , , and .
The elements at the level directly related to inline elements are:
and .
4.2.3.1 cp
Represents a Unicode character that is invalid in XML.
Contains:
This element is always empty.
Parents:
, , , and
Attributes:
- hex, REQUIRED
Example:
You can have the following fragment identifiers:
• #f=f1/u=u1/1 refers to the element of the source content of
the element .
• #f=f1/u=u1/t=1 refers to the element of the target content of
.
the element
• #f=f1/n=n1 refers to the element of the element
id="f1">.
• #f=f1/u=u1/n=n1 refers to the element of the element
.
• #f=f1/u=u1/s1 refers to the element of the element
.
• Assuming the extension defined by the namespace URI myNamespaceURI has
registered the prefix myprefix, the expression #f=f1/u=u1/myprefix=x1
of the element
refers to the element
id="u1">.
4 The Core Specification
XLIFF is a bilingual document format designed for containing text that needs
Translation, its corresponding translations and auxiliary data that makes the
Translation process possible.
At creation time, an XLIFF Document MAY contain only text in the source language.
Translations expressed in the target language MAY be added at a later time.
The root element of an XLIFF Document is . It contains a collection of
elements. Typically, each element contains a set of elements
that contain the text to be translated in the child of one or more
elements. Translations are stored in the child of each element.
4.1 General Processing Requirements
• An Agent processing a valid XLIFF Document that contains XLIFF-defined
elements and attributes that it cannot handle MUST preserve those elements
and attributes.
• An Agent processing a valid XLIFF Document that contains custom elements
and attributes that it cannot handle SHOULD preserve those elements and
attributes.
4.2 Elements
This section contains a description of all elements used in XLIFF Core.
4.2.1 Tree Structure
Legend:
1 = one
+ = one or more
? = zero or one
* = zero or more
4.2.2 Structural Elements
The structural elements used in XLIFF Core are: , , ,
, , , , , , ,
, and .
4.2.2.1 xliff
Root element for XLIFF documents.
Contains:
- One or more elements
Attributes:
- version, REQUIRED
- srcLang, REQUIRED
- trgLang, OPTIONAL
- xml:space, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The trgLang attribute is REQUIRED if and only if the XLIFF Document
contains elements that are children of or .
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- the its:versionattribute from the namespace
http://www.w3.org/2005/11/its, OPTIONAL.
4.2.2.2 file
Container for localization material extracted from an entire single document, or
another high level self contained logical node in a content structure that cannot be
described in the terms of documents.
Note
Sub-document artifacts such as particular sheets, pages, chapters
and similar are better mapped onto the element. The
element is intended for the highest logical level. For instance a
collection of papers would map to a single XLIFF Document, each
paper will be represented with one element, whereas chapters
and subsections will map onto nested elements.
Contains:
- Zero or one element followed by
- elements from other namespaces, OPTIONAL
- Zero or one element followed by
- One or more or elements in any order.
Attributes:
- id, REQUIRED
- canResegment, OPTIONAL
- original, OPTIONAL
- translate, OPTIONAL
- srcDir, OPTIONAL
- trgDir, OPTIONAL
- xml:space, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The following XLIFF Module elements are explicitly allowed by the wildcard
other:
- Zero or one elements
- Zero or one element
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero, one, or more elements
• Module and Extension elements MAY be used in any order.
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- attributes from the namespace urn:oasis:names:tc:xliff:fs:2.0, OPTIONAL,
provided that the Constraints specified in the Format Style Module are met.
- attributes from the namespace
urn:oasis:names:tc:xliff:sizerestriction:2.0, OPTIONAL, provided that
the Constraints specified in the Size and Length Restriction Module are met.
- attributes from the namespace http://www.w3.org/2005/11/its, OPTIONAL,
provided that the Constraints specified in the ITS Module are met.
- attributes from the namespace urn:oasis:names:tc:xliff:itsm:2.1,
OPTIONAL, provided that the Constraints specified in the ITS Module are met.
4.2.2.3 skeleton
Container for non-translatable material pertaining to the parent element.
Contains:
Either
- Non-translatable text
- elements from other namespaces
or
- is empty.
Attributes:
- href, OPTIONAL
Constraints
• The attribute href is REQUIRED if and only if the element is
empty.
Processing Requirements
• Modifiers and Enrichers processing an XLIFF Document that contains a
element MUST NOT change that element, its attributes, or its
content.
• Extractors creating an XLIFF Document with a element MUST
leave the element empty if and only if they specify the attribute
href.
4.2.2.4 group
Provides a way to organize units into a structured hierarchy.
Note that this is especially useful for mirroring a source format's hierarchical
structure.
Contains:
- elements from other namespaces, OPTIONAL
- Zero or one element followed by
- Zero, one or more or elements in any order.
Attributes:
- id, REQUIRED
- name, OPTIONAL
- canResegment, OPTIONAL
- translate, OPTIONAL
- srcDir, OPTIONAL
- trgDir, OPTIONAL
- type, OPTIONAL
- xml:space, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The following XLIFF Module elements are explicitly allowed by the wildcard
other:
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero, one, or more elements
• Module and Extension elements MAY be used in any order.
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- attributes from the namespace urn:oasis:names:tc:xliff:fs:2.0, OPTIONAL,
provided that the Constraints specified in the Format Style Module are met.
- attributes from the namespace
urn:oasis:names:tc:xliff:sizerestriction:2.0, OPTIONAL, provided that
the Constraints specified in the Size and Length Restriction Module are met.
- attributes from the namespace http://www.w3.org/2005/11/its, OPTIONAL,
provided that the Constraints specified in the ITS Module are met.
- attributes from the namespace urn:oasis:names:tc:xliff:itsm:2.1,
OPTIONAL, provided that the Constraints specified in the ITS Module are met.
4.2.2.5 unit
Static container for a dynamic structure of elements holding the extracted
translatable source text, aligned with the Translated text.
Contains:
- elements from other namespaces, OPTIONAL
- Zero or one elements followed by
- Zero or one element followed by
- One or more or elements in any order.
Attributes:
- id, REQUIRED
- name, OPTIONAL
- canResegment, OPTIONAL
- translate, OPTIONAL
- srcDir, OPTIONAL
- trgDir, OPTIONAL
- xml:space, OPTIONAL
- type, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• A MUST contain at least one element.
• The following XLIFF Module elements are explicitly allowed by the wildcard
other:
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero or one elements
- Zero, one, or more elements
- Zero, one, or more elements
• Module and Extension elements MAY be used in any order.
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- attributes from the namespace urn:oasis:names:tc:xliff:fs:2.0, OPTIONAL,
provided that the Constraints specified in the Format Style Module are met.
- attributes from the namespace
urn:oasis:names:tc:xliff:sizerestriction:2.0, OPTIONAL, provided that
the Constraints specified in the Size and Length Restriction Module are met.
- attributes from the namespace http://www.w3.org/2005/11/its, OPTIONAL,
provided that the Constraints specified in the ITS Module are met.
- attributes from the namespace urn:oasis:names:tc:xliff:itsm:2.1,
OPTIONAL, provided that the Constraints specified in the ITS Module are met.
4.2.2.6 segment
This element is a container to hold in its aligned pair of children elements the
minimum portion of translatable source text and its Translation in the given
Segmentation.
Contains:
- One element followed by
- Zero or one element
Attributes:
- id, OPTIONAL
- canResegment, OPTIONAL
- state, OPTIONAL
- subState, OPTIONAL
4.2.2.7 ignorable
Part of the extracted content that is not included in a segment (and therefore not
translatable). For example tools can use to store the white space
and/or codes that are between two segments.
Contains:
- One element followed by
- Zero or one element
Attributes:
- id, OPTIONAL
4.2.2.8 notes
Collection of comments.
Contains:
- One or more elements
4.2.2.9 note
This is an XLIFF specific way how to present end user readable comments and
annotations. A note can contain information about , , ,
, or elements.
Contains:
- Text
Attributes:
- id, OPTIONAL
- appliesTo, OPTIONAL
- category, OPTIONAL
- priority, OPTIONAL
- attributes from other namespaces, OPTIONAL
Constraints
• The following XLIFF Module attributes are explicitly allowed by the wildcard
other:
- fs:fs, OPTIONAL
- fs:subFs, OPTIONAL
4.2.2.10 originalData
Unit-level collection of original data for the inline codes.
Contains:
- One or more elements
4.2.2.11 data
Storage for the original data of an inline code.
Contains:
- Non-translatable text
- Zero, one or more elements.
Non-translatable text and elements MAY appear in any order.
Attributes:
- id, REQUIRED
- dir, OPTIONAL
- xml:space, OPTIONAL, the value is restricted to preserve on this element
4.2.2.12 source
Portion of text to be translated.
Contains:
- Text
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
Text and inline elements may appear in any order.
Attributes:
- xml:lang, OPTIONAL
- xml:space, OPTIONAL
Constraints
• When a element is a child of or , the
explicit or inherited value of the OPTIONAL xml:lang attribute MUST be
equal to the value of the srcLang attribute of the enclosing element.
4.2.2.13 target
The translation of the sibling element.
Contains:
- Text
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
- Zero, one or more elements
Text and inline elements may appear in any order.
Attributes:
- xml:lang, OPTIONAL
- xml:space, OPTIONAL
- order, OPTIONAL
Constraints
• When a element is a child of or , the
explicit or inherited value of the OPTIONAL xml:lang MUST be equal to the
value of the trgLang attribute of the enclosing element.
4.2.3 Inline Elements
The XLIFF Core inline elements at the or level are: , ,
, , , , and .
The elements at the level directly related to inline elements are:
and .
4.2.3.1 cp
Represents a Unicode character that is invalid in XML.
Contains:
This element is always empty.
Parents:
, , , and
Attributes:
- hex, REQUIRED
Example:
Ctrl+C=
The example above shows a character U+0003 (Control C) as it has to be
represented in XLIFF.
Processing Requirements
• Writers MUST encode all invalid XML characters of the content using .
• Writers MUST NOT encode valid XML characters of the content using .
4.2.3.2 ph
Represents a standalone code of the original format.
Contains:
This element is always empty.
Parents: , , and
Attributes:
- canCopy, OPTIONAL
- canDelete, OPTIONAL
- canReorder, OPTIONAL
- copyOf, OPTIONAL
- disp, OPTIONAL
- equiv, OPTIONAL
- id, REQUIRED.
- dataRef, OPTIONAL
- subFlows, OPTIONAL
- subType, OPTIONAL
- type, OPTIONAL
- attributes from other namespaces, OPTIONAL
Example:
%d
<br/>
Number of entries:
dataRef="d2"/>(These entries are only the ones matching the
current filter settings)
Constraints
• The following XLIFF Modul ...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
ISO 18587:2017 provides requirements for the process of full, human post-editing of machine translation output and post-editors' competences. ISO 18587:2017 is intended to be used by TSPs, their clients, and post-editors. It is only applicable to content processed by MT systems. NOTE For translation services in general, see ISO 17100.
This document specifies a framework for representing data recorded in terminological data collections (TDCs). This framework includes a metamodel and methods for describing specific terminological markup languages (TMLs), exemplified in this document in eXtensible Markup Language (XML). The mechanisms for implementing constraints in a TML are defined, but not the specific constraints for individual TMLs. This document is designed to support the development and use of computer applications for terminological data and the exchange of such data between different applications. This document also defines the conditions that allow the data expressed in one TML to be mapped onto another TML.
This document specifies Schematron, a schema language for XML. This document establishes requirements for Schematron schemas and specifies when an XML document matches the patterns specified by a Schematron schema. Schematron uses query languages such as XPath for writing assertions.
This document provides requirements and recommendations for the structure and associated metadata to be included and the governance of the Global Media Identifier (GMI) that can be assigned to all media outlets that publish content online. The identification of material or physical objects is out of scope of this document. This document also considers the GMI’s technical infrastructure and its practical implementation. It is a neutral, non-judgemental numbering or naming convention, not a certification scheme. This document does not include any provisions for the assessment of online content, e.g. as regards its trustworthiness, quality, or an outlet’s conformance with journalistic standards.
This document defines the layout and colorimetric values of targets for use in the calibration of a photographic product/input scanner combination (as used in the preparatory process for printing and publishing). One target is defined for positive colour transparency film and another is defined for colour photographic paper.
This document specifies methods for extracting candidate terms from text corpora and gives guidance on selecting relevant designations, definitions, concept relations and other terminology-related information.
This document specifies requirements and recommendations for representing subject fields and concept relations in TBX-compliant terminological document instances. Examples in this document utilize the data category as attribute (DCA) style of TBX markup.
This document provides a data model and encoding rules for the use of radio frequency identification (RFID) tags for items appropriate for the needs of all types of libraries (including national, academic, public, corporate, special, and school libraries). This document specifies the rules for encoding - a subset of data elements taken from the total set of data elements listed in ISO 28560-1 into a basic block, and - other data elements into extension blocks onto the RFID tag. A source of additional information about implementation issues is provided in Annex A.
This document provides user interface requirements and functional description of real-time automatic simultaneous interpretation systems designed to interoperate among different natural languages for spontaneous speech. While traditional speech to speech translation addresses the functional equivalent of consecutive interpretation, this document focuses on the functional equivalent of simultaneous interpretation. This document does not cover sign language interpretation.
This document provides the general description of real-time automatic simultaneous interpretation systems designed to interoperate among different natural languages for spontaneous speech. While traditional speech to speech machine translation addresses the functional equivalent of consecutive interpretation, this document focuses on the functional equivalent of simultaneous interpretation. This document does not cover sign language interpretation.
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...