XLIFF (XML Localization Interchange File Format) is an
XML
Extensible Markup Language (XML) is a markup language and file format for storing, transmitting, and reconstructing data. It defines a set of rules for encoding electronic document, documents in a format that is both human-readable and Machine-r ...
-based
bitext
A parallel text is a text placed alongside its translation or translations. Parallel text alignment is the identification of the corresponding sentences in both halves of the parallel text. The Loeb Classical Library and the Clay Sanskrit Libr ...
format created to standardize the way localizable data are passed between and among tools during a localization process and a common format for CAT tool exchange. The XLIFF Technical Committee (TC) first convened at
OASIS
In ecology, an oasis (; : oases ) is a fertile area of a desert or semi-desert environment but the first fully ratified version of XLIFF appeared as XLIFF Version 1.2 in February 2008. Its current specification is v2.1 released on 2018-02-13, which is backwards compatible with v2.0 released on 2014-08-05.
The specification is aimed at the localization industry. It specifies elements and attributes to store content extracted from various original file formats and its corresponding translation. The goal was to abstract the localization skills from the engineering skills related to specific formats such as HTML.
XLIFF is part of the Open Architecture for XML Authoring and Localization ( OAXAL) reference architecture.
XLIFF 2.0 and higher (the current OASIS ratified format)
The XLIFF Technical Committee (TC) is currently preparing to start working on XLIFF Version 2.2.
Prior to making of the major new version 2.0, feedback was gathered from XLIFF's user community which was integrated into the following generation version of the standard. Two of the primary methods used included compiling a list of extensions used by XLIFF toolmakers, and compiling a list of XLIFF features supported by each XLIFF tool.
* Makers of XLIFF tools have taken advantage of XLIFF's extensibility mechanism in order to implement a number of features. By collecting a list of these extension points and analyzing them for common tasks, the XLIFF TC hopes to improve the XLIFF 2.0 Specification to include mechanisms that will enable the toolmakers to support these features without using extensibility.
* Makers of XLIFF tools have supported different sets of features in the XLIFF 1.2 Specification. By compiling a list of these features, the XLIFF TC hopes to identify areas where the XLIFF 2.0 Specification can be improved to enable toolmakers to more widely support the specification.
On February 13, 2018 XLIFF 2.1 specification became an OASIS Standard.
In November, 2017 XLIFF 2.0 specification was approved as ISO 21720:2017.
On August 6, 2014 the XLIFF 2.0 specification became an OASIS Standard.
On May 6, 2014, the XLIFF 2.0 specification was moved to Candidate OASIS Standard.
Example of an XLIFF 2.0 document:
QuetzalQuetzalAn application to manipulate and process XLIFF documentsXLIFF 文書を編集、または処理 するアプリケーションです。XLIFF Data ManagerXLIFF データ・マネージャ
XLIFF 1.2 - legacy format
An XLIFF 1.2 document is composed of one or more <file> elements. Each <file> element corresponds to an original file or source (e.g. database table). A <file> contains the source of the localizable data and, once translated, the corresponding localized data for one, and only one, locale.
Localizable data is stored in <trans-unit> elements. The <trans-unit> element holds a <source> element to store the source text, and a <target> element to store the latest translated text. The <target> elements are not mandatory.
Cannot find the file.Fichier non trouvé.
The example below shows an XLIFF document storing text extracted from a Photoshop file (PSD file) and its translation to Japanese:
Make sure to use the glossary I sent you yesterday.
Thanks.QuetzalQuetzalAn application to manipulate and
process XLIFF documentsXLIFF 文書を編集、または処理
するアプリケーションです。XLIFF Data ManagerXLIFF データ・マネージャ