XLIFF

Last updated
XLIFF
Filename extension
.xlf
Internet media type
before 2.0: application/x-xliff+xml (private), 2.0 and after: application/xliff+xml (standard tree)
Latest release
2.1 [1]
13 February 2018;5 years ago (2018-02-13)
Extended from XML
Standard OASIS Standard, also ratified as ISO 21720:2017
Website http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html

XLIFF (XML Localization Interchange File Format) is an XML-based bitext 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 December 2001 (first meeting in January 2002), [2] but the first fully ratified version of XLIFF appeared as XLIFF Version 1.2 in February 2008. Its current specification is v2.1 [1] released on 2018-02-13, which is backwards compatible with v2.0 released on 2014-08-05.

Contents

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. [3]

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 is currently preparing to start working on XLIFF Version 2.2. [4] 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.

On February 13, 2018 XLIFF 2.1 specification became an OASIS Standard. [5]

In November, 2017 XLIFF 2.0 specification was approved as ISO 21720:2017. [6]

On August 6, 2014 the XLIFF 2.0 specification became an OASIS Standard. [7]

On May 6, 2014, the XLIFF 2.0 specification was moved [8] to Candidate OASIS Standard. [9]

Example of an XLIFF 2.0 document:

<xliffxmlns="urn:oasis:names:tc:xliff:document:2.0"version="2.0"srcLang="en-US"trgLang="ja-JP"><fileid="f1"original="Graphic Example.psd"><skeletonhref="Graphic Example.psd.skl"/><unitid="1"><segment><source>Quetzal</source><target>Quetzal</target></segment></unit><unitid="2"><segment><source>AnapplicationtomanipulateandprocessXLIFFdocuments</source><target>XLIFF文書を編集、または処理するアプリケーションです。</target></segment></unit><unitid="3"><segment><source>XLIFFDataManager</source><target>XLIFFデータ・マネージャ</target></segment></unit></file></xliff>

XLIFF 1.2 - legacy format

An XLIFF 1.2 [10] 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.

<trans-unitid="1"><sourcexml:lang="en">Cannotfindthefile.</source><targetxml:lang="fr">Fichiernontrouvé.</target></trans-unit>

The example below shows an XLIFF document storing text extracted from a Photoshop file (PSD file) and its translation to Japanese:

<xliffversion="1.2"><fileoriginal="Graphic Example.psd"source-language="en-US"target-language="ja-JP"tool="Rainbow"datatype="photoshop"><header><skl><external-fileuid="3BB236513BB24732"href="Graphic Example.psd.skl"/></skl><phase-group><phasephase-name="extract"process-name="extraction"tool="Rainbow"date="20010926T152258Z"company-name="NeverLand Inc."job-id="123"contact-name="Peter Pan"contact-email="ppan@example.com"><note>MakesuretousetheglossaryIsentyouyesterday. Thanks.</note></phase></phase-group></header><body><trans-unitid="1"maxbytes="14"><sourcexml:lang="en-US">Quetzal</source><targetxml:lang="ja-JP">Quetzal</target></trans-unit><trans-unitid="3"maxbytes="114"><sourcexml:lang="en-US">AnapplicationtomanipulateandprocessXLIFFdocuments</source><targetxml:lang="ja-JP">XLIFF文書を編集、または処理 するアプリケーションです。</target></trans-unit><trans-unitid="4"maxbytes="36"><sourcexml:lang="en-US">XLIFFDataManager</source><targetxml:lang="ja-JP">XLIFFデータ・マネージャ</target></trans-unit></body></file></xliff>

See also

Related Research Articles

A translation memory (TM) is a database that stores "segments", which can be sentences, paragraphs or sentence-like units that have previously been translated, in order to aid human translators. The translation memory stores the source text and its corresponding translation in language pairs called “translation units”. Individual words are handled by terminology bases and are not within the domain of TM.

The Organization for the Advancement of Structured Information Standards is a nonprofit consortium that works on the development, convergence, and adoption of open standards for cybersecurity, blockchain, Internet of things (IoT), emergency management, cloud computing, legal data exchange, energy, content technologies, and other areas.

The Open Document Format for Office Applications (ODF), also known as OpenDocument, is an open file format for word processing documents, spreadsheets, presentations and graphics and using ZIP-compressed XML files. It was developed with the aim of providing an open, XML-based file format specification for office applications.

The Darwin Information Typing Architecture (DITA) specification defines a set of document types for authoring and organizing topic-oriented information, as well as a set of mechanisms for combining, extending, and constraining document types. It is an open standard that is defined and maintained by the OASIS DITA Technical Committee.

Translation Memory eXchange (TMX) is an XML specification for the exchange of translation memory (TM) data between computer-aided translation and localization tools with little or no loss of critical data.

<span class="mw-page-title-main">Okapi Framework</span>

The Okapi Framework is a cross-platform and open-source set of components and applications that offer extensive support for localizing and translating documentation and software.

<span class="mw-page-title-main">Wordfast</span>

The name Wordfast is used for any number of translation memory products developed by Wordfast LLC. The original Wordfast product, now called Wordfast Classic, was developed by Yves Champollion in 1999 as a cheaper alternative to Trados, a well-known translation memory program. The current Wordfast products run on a variety of platforms but use largely compatible translation memory formats, and often also have similar workflows. The software is most popular with freelance translators, although some of the products are also suited for corporate environments.

OAXAL: Open Architecture for XML Authoring and Localization is an Organization for the Advancement of Structured Information Standards (OASIS) standards-based initiative to encourage the development of an open Standards approach to XML Authoring and Localization. OAXAL is an official OASIS Reference Architecture Technical Committee.

Security Assertion Markup Language 2.0 (SAML 2.0) is a version of the SAML standard for exchanging authentication and authorization identities between security domains. SAML 2.0 is an XML-based protocol that uses security tokens containing assertions to pass information about a principal between a SAML authority, named an Identity Provider, and a SAML consumer, named a Service Provider. SAML 2.0 enables web-based, cross-domain single sign-on (SSO), which helps reduce the administrative overhead of distributing multiple authentication tokens to the user. SAML 2.0 was ratified as an OASIS Standard in March 2005, replacing SAML 1.1. The critical aspects of SAML 2.0 are covered in detail in the official documents SAMLCore, SAMLBind, SAMLProf, and SAMLMeta.

The Translate Toolkit is a localization and translation toolkit. It provides a set of tools for working with localization file formats and files that might need localization. The toolkit also provides an API on which to develop other localization tools.

<span class="mw-page-title-main">Virtaal</span>

Virtaal is a computer-assisted translation tool written in the Python programming language. It is free software developed and maintained by Translate.org.za.

Content Assembly Mechanism (CAM) is an XML-based standard for creating and managing information exchanges that are interoperable and deterministic descriptions of machine-processable information content flows into and out of XML structures. CAM is a product of the OASIS Content Assembly Technical Committee.

Trados Studio is a computer-assisted translation software tool which offers a complete, centralized translation environment for editing, reviewing and managing translation projects and terminology – It can be used both offline in a desktop tool or online in the cloud. Trados Studio is part of the Trados product portfolio, which is a suite of intelligent translation products owned by RWS that enables freelance translators, language service providers (LSPs) and corporations to streamline processes and improve efficiencies while keeping costs down.

Open Language Tools is a Java project released by Sun Microsystems under the terms of Sun's CDDL.

openTMS is an acronym for Open Source Translation Management System.

Swordfish Translation Editor is a Computer-assisted translation software.

The Service-Oriented Localisation Architecture Solution, or SOLAS, enables the global conversation in communities and is an open source project of The Rosetta Foundation.

memoQ is a proprietary computer-assisted translation software suite which runs on Microsoft Windows operating systems. It is developed by the Hungarian software company memoQ Fordítástechnológiai Zrt., formerly Kilgray, a provider of translation management software established in 2004 and cited as one of the fastest-growing companies in the translation technology sector in 2012 and 2013. memoQ provides translation memory, terminology, machine translation integration and reference information management in desktop, client/server and web application environments.

TermBase eXchange (TBX) is an international standard for the representation of structured concept-oriented terminological data, copublished by ISO and the Localization Industry Standards Association (LISA). Originally released in 2002 by LISA's OSCAR special interest group, TBX was adopted by ISO TC 37 in 2008. In 2019 ISO 30042:2008 was withdrawn and revised by ISO 30042:2019. It is currently available as an ISO standard and as an open, industry standard, available at no charge.

The SAML metadata standard belongs to the family of XML-based standards known as the Security Assertion Markup Language (SAML) published by OASIS in 2005. A SAML metadata document describes a SAML deployment such as a SAML identity provider or a SAML service provider. Deployments share metadata to establish a baseline of trust and interoperability.

References

  1. 1 2 "XLIFF Version 2.1". docs.oasis-open.org.
  2. OASIS XML Localisation Interchange File Format Technical Committee. "XLIFF TC Charter". OASIS. Retrieved 2020-07-28.
  3. Bert Esselink (2003). The Evolution of Localization (PDF). Guide to Localization. Multilingual Computing and Technology. Does the popularity of XLIFF signal a trend? Throughout the 1990s, the localization industry tried to turn translators into semi-engineers. Is it now expecting them to just translate again? It certainly looks that way.
  4. "FeatureTracking - XLIFF Wiki". wiki.oasis-open.org.
  5. "#XLIFF V2.1 becomes an OASIS Standard | OASIS". www.oasis-open.org.
  6. "ISO 21720:2017". ISO.
  7. "XLIFF Version 2.0 becomes an OASIS Standard | OASIS". www.oasis-open.org.
  8. "60-day Public Review for XLIFF Version 2.0 Candidate OASIS Standard - en". lists.oasis-open.org.
  9. "XLIFF Version 2.0". docs.oasis-open.org.
  10. "XLIFF 1.2 Specification". docs.oasis-open.org.