{"history":[],"article":{"id":"c7560a0f-f28e-4091-a209-89a0b7d61f55","title":"XLIFF","slug":"xliff","content":":::summary\n**Name:** XLIFF \n**Extension:** .xlf \n**Mime:** before 2.0: application/x-xliff+xml (private), 2.0 and after: application/xliff+xml (standard tree) \n**Latest Release Version:** 2.1 \n**Latest Release Date:** February 13, 2018 \n**Extended From:** [XML](https://bliptext.com/articles/xml) \n**Standard:** OASIS Standard, also ratified as ISO 21720:2017 \n**URL:** http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html \n:::\n\n# \n**XLIFF** (**[XML](https://bliptext.com/articles/xml) Localization Interchange File Format**) is an [XML](https://bliptext.com/articles/xml)-based [bitext](https://bliptext.com/articles/bitext) format created to standardize the way localizable data are passed between and among tools during a [localization](https://bliptext.com/articles/internationalization-and-localization) process and a common format for [CAT tool](https://bliptext.com/articles/cat-tool) exchange.\nThe XLIFF Technical Committee (TC) first convened at [OASIS](https://bliptext.com/articles/oasis-organization) in December 2001 (first meeting in January 2002), but the first fully ratified version of XLIFF appeared as XLIFF Version 1.2 in February 2008.\nIts current specification is v2.1 released on 2018-02-13, which is backwards compatible with v2.0 released on 2014-08-05.\nThe specification is aimed at the localization industry.\nIt specifies elements and attributes to store content extracted from various original file formats and its corresponding translation.\nThe goal was to abstract the localization skills from the engineering skills related to specific formats such as HTML.\nXLIFF is part of the [Open Architecture](https://bliptext.com/articles/open-architecture) for XML Authoring and Localization ([OAXAL](https://bliptext.com/articles/oaxal)) reference architecture.\n\n# XLIFF 2.0 and higher (the current OASIS ratified format)\nThe XLIFF Technical Committee (TC) is currently preparing to start working on XLIFF Version 2.2.\nPrior 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.\nTwo 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.\nOn February 13, 2018 XLIFF 2.1 specification became an OASIS Standard.\nIn November, 2017 XLIFF 2.0 specification was approved as ISO 21720:2017.\nOn August 6, 2014 the XLIFF 2.0 specification became an OASIS Standard.\nOn May 6, 2014, the XLIFF 2.0 specification was moved to Candidate OASIS Standard.\nExample of an XLIFF 2.0 document:\nQuetzal\nXLIFF 文書を編集、または処理するアプリケーションです.\nXLIFF データ・マネージャ\n\n# XLIFF 1.2 - legacy format\nAn XLIFF 1.2 document is composed of one or more elements.\nEach element corresponds to an original file or source (e.g. database table).\nA contains the source of the localizable data and, once translated, the corresponding localized data for one, and only one, locale.\nLocalizable data is stored in elements.\nThe element holds a element to store the source text, and a element to store the latest translated text.\nThe elements are not mandatory.\nFichier non trouvé.\n\nThe example below shows an XLIFF document storing text extracted from a Photoshop file (PSD file) and its translation to Japanese:\nQuetzal\n\n\nXLIFF 文書を編集、または処理\nするアプリケーションです.\n\n\nXLIFF データ・マネージャ\n","current_revision":null,"created_by":"kACnuQmH5k9Nr5VNVEpVeg7XpvUmMctD","created_at":"2025-01-26T09:35:35.800Z","updated_at":"2025-01-26T09:35:35.800Z","search_vector":"'xliff':1","search_content":" \n**Name:** XLIFF \n**Extension:** .xlf \n**Mime:** before 2.0: application/x-xliff+xml (private), 2.0 and after: application/xliff+xml (standard tree) \n**Latest Release Version:** 2.1 \n**Latest Release Date:** February 13, 2018 \n**Extended From:** [XML](https://bliptext.com/articles/xml) \n**Standard:** OASIS Standard, also ratified as ISO 21720:2017 \n**URL:** http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html \n \n\n# \n**XLIFF** (**[XML](https://bliptext.com/articles/xml) Localization Interchange File Format**) is an [XML](https://bliptext.com/articles/xml)-based [bitext](https://bliptext.com/articles/bitext) format created to standardize the way localizable data are passed between and among tools during a [localization](https://bliptext.com/articles/internationalization-and-localization) process and a common format for [CAT tool](https://bliptext.com/articles/cat-tool) exchange.\nThe XLIFF Technical Committee (TC) first convened at [OASIS](https://bliptext.com/articles/oasis-organization) in December 2001 (first meeting in January 2002), but the first fully ratified version of XLIFF appeared as XLIFF Version 1.2 in February 2008.\nIts current specification is v2.1 released on 2018-02-13, which is backwards compatible with v2.0 released on 2014-08-05.\nThe specification is aimed at the localization industry.\nIt specifies elements and attributes to store content extracted from various original file formats and its corresponding translation.\nThe goal was to abstract the localization skills from the engineering skills related to specific formats such as HTML.\nXLIFF is part of the [Open Architecture](https://bliptext.com/articles/open-architecture) for XML Authoring and Localization ([OAXAL](https://bliptext.com/articles/oaxal)) reference architecture.\n\n# XLIFF 2.0 and higher (the current OASIS ratified format)\nThe XLIFF Technical Committee (TC) is currently preparing to start working on XLIFF Version 2.2.\nPrior 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.\nTwo 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.\nOn February 13, 2018 XLIFF 2.1 specification became an OASIS Standard.\nIn November, 2017 XLIFF 2.0 specification was approved as ISO 21720:2017.\nOn August 6, 2014 the XLIFF 2.0 specification became an OASIS Standard.\nOn May 6, 2014, the XLIFF 2.0 specification was moved to Candidate OASIS Standard.\nExample of an XLIFF 2.0 document:\nQuetzal\nXLIFF 文書を編集、または処理するアプリケーションです.\nXLIFF データ・マネージャ\n\n# XLIFF 1.2 - legacy format\nAn XLIFF 1.2 document is composed of one or more elements.\nEach element corresponds to an original file or source (e.g. database table).\nA contains the source of the localizable data and, once translated, the corresponding localized data for one, and only one, locale.\nLocalizable data is stored in elements.\nThe element holds a element to store the source text, and a element to store the latest translated text.\nThe elements are not mandatory.\n Fichier non trouvé.\n \nThe example below shows an XLIFF document storing text extracted from a Photoshop file (PSD file) and its translation to Japanese:\n Quetzal\n \n \n XLIFF 文書を編集、または処理\nするアプリケーションです.\n \n \n XLIFF データ・マネージャ\n ","revisionCount":0},"hasMore":false,"nextCursor":null}

History