open language tools xliff translation editor

#OPEN LANGUAGE TOOLS XLIFF TRANSLATION EDITOR HOW TO#
#OPEN LANGUAGE TOOLS XLIFF TRANSLATION EDITOR SOFTWARE#

The vocabularies will support common software and content data formats. The vocabularies will be tool-neutral, support the localization-related aspects of internationalization and the entire localization process. The specification will provide the ability to mark up and capture localizable data and interoperate with different processes or phases without loss of information. From the XLIFF TC Charter 2002-07: 'The purpose of the OASIS XLIFF TC is to define, through XML vocabularies an extensible specification for the interchange of localization information.

To encourage adoption of XLIFF, the TC will define and publish implementation guides for some of the most commonly used resource formats (HTML, Java Resource Bundles, and gettext PO Files). The next phase consists of promoting the adoption of XLIFF throughout the industry through additional collateral and specifications, continuing to advance the committee specification towards an official OASIS standard, and revising the XLIFF spec to 1.2 version to support document based content segmentation and alignment requirements. The first phase, completed 31-October-2003, created a 1.1 version committee specification that concentrated on software UI resource file localisable data requirements. For software developers and technical communicators employing enterprise localisation tools and processes, XLIFF defines a standard but extensible vocabulary that captures relevant metadata for any point in the lifecycle which can be exchanged between a variety of commercial and open-source tools. For publishers with many proprietary or non-standard formats, this requirement becomes a major hurdle when attempting to localise their software. Using proprietary and/or non-standard resource formats force either the source provider or the localisation service provider to implement costly and inefficient pre-processing of localisable content. Once software providers and technical communicators commenced implementing XLIFF, the task of interchanging localisation data was simplified. The state of software and documentation localisation before XLIFF was that a software or documentation provider delivered their localisable resources to a localisation service provider in a number of disparate file formats. The extensibility mechanism provides controlled inclusion of information not defined in the specification. The specifications provide an extensibility mechanism to allow the development of tools compatible with an implementer's data formats and workflow requirements.

The specifications are tool-neutral, support the entire localization process, and support common software and document data formats and mark-up languages.

#OPEN LANGUAGE TOOLS XLIFF TRANSLATION EDITOR HOW TO#

To date, the committee has published two specifications - XLIFF 1.0 and XLIFF 1.1 - that define how to mark up and capture localisable data that will interoperate with different processes or phases without loss of information. The purpose of the OASIS XML Localisation Interchange File Format (XLIFF) TC is to define, through extensible XML vocabularies, and promote the adoption of, a specification for the interchange of localisable software and document based objects and related metadata. As described in the TC Charter Clarification of June 2006: XLIFF has a working relationship with LISA/OSCAR standards related to Translation and Localization, and is a requirement for several LISA standards: (1) TMX supports XLIFF inline markup, where TMX Version 2.0 was in progress as of Ma(2) Global Information Management Metrics eXchange (GMX), where XLIFF is a requirement (3) xml:tm, where XLIFF is a requirement. Use of XLIFF is represented in the DITA Translation Subcommittee, and will be featured in a translation best practices document. The specification provides an extensibility mechanism to allow the development of tools compatible with an implementer's data formats and workflow requirements. The specification is tool-neutral, supports the entire localization process, and supports common software, document data formats, and mark-up languages. 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 tools. The XLIFF 1.2 Specification defines the XML Localization Interchange File Format (XLIFF). In February 2008, OASIS announced the approval of XLIFF v1.2 as an OASIS Standard: see New OASIS Standard: XML Localization Interchange File Format (XLIFF) v1.2.

General: News, Articles, Reports, Drafts.

Open language tools xliff translation editor