LLMpediaThe first transparent, open encyclopedia generated by LLMs

XLIFF

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: gettext Hop 4
Expansion Funnel Raw 95 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted95
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
XLIFF
NameXLIFF
Extension.xlf, .xliff
Mimeapplication/x-xliff+xml
GenreLocalization interchange format

XLIFF

Introduction

XLIFF is an XML-based localization interchange file format designed to standardize the exchange of localization and translation data among tools and organizations. It enables interoperability between vendors such as SDL (company), memoQ, OmegaT, Wordfast, and Google Translate integrations, and is used by institutions like Microsoft, IBM, Adobe Systems, LinkedIn, and Apple Inc. to streamline workflows involving assets from Microsoft Office, HTML, DocBook, OpenDocument Format, and Android (operating system) resources.

History and Development

The format originated in efforts coordinated by localization industry groups and standards bodies including OASIS (organization), where contributors from Sun Microsystems, Nokia, Yahoo!, Oracle Corporation, SAP SE, and Amazon (company) collaborated. Early implementations referenced tools from Trados, SDL Trados Studio, and proprietary systems used by European Commission projects and United Nations language services. Subsequent revisions involved stakeholders such as GitHub, Mozilla Foundation, Facebook, Twitter, and Cisco Systems to address web and mobile workloads, with influence from standards like XML and guidelines from W3C.

File Format and Structure

An XLIFF document is structured as an XML container that encapsulates translatable units, metadata, and resource references compatible with workflows from Subversion, GitLab, Jenkins (software), and Atlassian integrations. Core components include file-level headers, body segments containing elements, and optional groups for context, enabling cross-references to artifacts from Microsoft Word, Adobe InDesign, LaTeX, Markdown, and JSON (JavaScript object notation) serializations. Implementers often map XLIFF assets to content management systems such as Drupal, WordPress, SharePoint, and Confluence (software).

Core Features and Extensions

Key features support segmentation, inline tags, placeholders, and metadata attributes aligning with workflows from Continuous Integration pipelines used by Google Cloud Platform, Amazon Web Services, Microsoft Azure, and Heroku. Extensions and profiles have been developed to support specific domains, including mobile localization tied to Android (operating system) resource XML, web localization tied to HTML5 and ECMAScript, and technical translation workflows used by Red Hat, Intel, Qualcomm, and Siemens. Community extensions reference schemas influenced by ISO/IEC standards and coordination with projects like OpenASTM and corporate localization teams at eBay, Airbnb, and Uber Technologies.

Tools and Implementations

A wide ecosystem provides tooling and runtime support, spanning desktop CAT tools such as SDL Trados Studio, memoQ, Wordfast, and Déjà Vu (translators' tool); open-source converters like Okapi Framework; server platforms from Smartling, Transifex, Crowdin, Phrase (software); and automation integrations used by Jenkins (software), GitHub Actions, GitLab CI/CD, and CircleCI. Internationalization libraries in languages supported by Python (programming language), Java (programming language), JavaScript, Ruby (programming language), and Go (programming language) provide parsers and serializers for pipeline integration with products from Atlassian, Slack, and Zendesk.

Use Cases and Adoption

Adoption spans enterprise product localization at Microsoft, Google, Apple Inc., and Amazon (company), open-source projects like Mozilla Firefox, LibreOffice, and WordPress, as well as government translation projects at European Commission, United Nations, World Health Organization, and NATO. Typical uses include software string translation for Android (operating system) and iOS, website localization for W3C-compliant sites, documentation workflows for Apache Software Foundation projects, and multimedia subtitle exchange compatible with SubRip and WebVTT pipelines used by Netflix and YouTube.

Standards and Governance

Governance and versioning decisions have been managed through standards bodies and consortiums such as OASIS (organization), with contributions and implementations across corporations including IBM, Oracle Corporation, SAP SE, and Microsoft. Compatibility concerns and best practices reference other standards like XML, ISO/IEC 19510, and guidelines from W3C, while industry conferences and working groups involving LocWorld, TAUS, GALA (Globalization and Localization Association), and XCON drive recommendations and adoption strategies.

Category:Localization