Download presentation
Presentation is loading. Please wait.
Published byAllan McLaughlin Modified over 5 years ago
1
XLIFF 2 Industry Update David Filip, Uwe Stahlschmidt & Daniel Goldschmidt CNGL/ADAPT & Microsoft
2
Intro The XLIFF 2.0 OASIS Standard was officially released last August. We will inform the L10n community about XLIFF 2.0 adoption in the industry and will also cover XLIFF 2.x plans – adding new features in a nimble way... How a big corporation like Microsoft benefits from co-developing and adopting XLIFF 2.0
3
What is XLIFF? XML Localisation/Localization Interchange File Format
The only open standard bitext format XLIFF 1.2 OASIS Standard since Feb 2008 Superseded by XLIFF 2.0 in August 2014
4
XLIFF 1.2 Issues XLIFF TC convened 2001 (long time ago)
XLIFF 1.x suffers from feature creep, BUT at the same time is “terrifyingly slim” overlapping features due to overreliance on compromise ambiguity, lack of processing requirements too much extensibility incompatible implementations as result Despite of all of the above still a huge success! Microsoft, Oracle, Lionbridge et al.
5
Microsoft and XLIFF 1.2 Single implementation of XLIFF 1.2 agreed across Microsoft Created common toolset Evangelized benefits of XLIFF Windows division: XLIFF used for all content localization Standardized workflow and tools Integration in Microsoft products MultiLingual App Toolkit Integrates with Visual Studio’s IDE Uses common Microsoft XLIFF 1.2 Object Model Export & import for translators Dedicated translation editor Easily build multilingual apps for Windows 8 and Windows Phone SharePoint 2013 Improved support for multilingual sites in SharePoint 2013 XLIFF 1.2 for export/import of localization data First commercial implementation of XLIFF text + binary localization
6
XLIFF 1.2 Localization Workflow
Microsoft Engineering Excellence XLIFF 1.2 Localization Workflow XLIFF parsing Validation XML check-in XML check-in Recycling Cloud-based Localization Workflow Content Publishing Systems Localization Source Control Handback Handoff Localization Service Providers Typical workflow utilizing XLIFF 1.2: Content is created in Content Publishing System Source file (English, in XML format) is checked into Source Control System The Cloud-based Localization Workflow System monitors the Source Control System, picks up new/updated files and converts to XLIFF 1.2 Recycling and Validation services are run befor hand-off to localization suppliers After that, files are handed off to localization suppliers for translation Localization Service providers perform translation services Localization Service providers hand-back translated files into Cloud-based Localization Workflow System The Cloud-based Localization Workflow System converts the translated XLIFF 1.2 files into original XML format and check them into the Source Control System The localized files are propagated to the Content Publishing System for publishing Microsoft Confidential
7
Getting to “One XLIFF at Microsoft”
Education Shared best practices, provided training Socialized XLIFF Supported trials, tracked progress, sought buy-in Industry liaison XLIFF TC, Microsoft-wide goals Tools & technologies Common Object Model, code samples
8
XLIFF 2 Overview Conformance Clause Modular Design
Small non-negotiable core Advanced features through modules Conformance Clause Document Conformance Targets XSD and Advanced Constraints Application Conformance Targets Agent Classification
9
Modular Design Mandatory Core Modules Optional Extensions Custom
10
Intent of Modular Design
Interoperability Adaptability Core Modules Extensions NON-Negotiable Guaranteed roundtrip Optional Guaranteed survival Custom/private Application specific Should survive roundtrip
11
XLIFF 2 Overview - Agents
Writer Extractor, Enricher, e.g. reviewer workbench, TM server, MT broker etc. Modifier, e.g. a translation editor Merger Etc. e.g. validator
12
XLIFF 2 Overview - Core About 20% of XLIFF 1.2 feature set
An extremely good thing for interoperability Roundtrip oriented New segmentation model New inline text model All and only features that are necessary to roundtrip source with target translations
13
XLIFF 2 Overview - Modules
All else are OPTIONAL features available through MODULES – Translation Candidates Module – Glossary Module – Format Style Module – Metadata Module – Resource Data Module – Change Tracking Module – Size and Length Restriction Module – Validation Module
14
XLIFF 2 targets an open ecosystem of best of breed specialized tools
XLIFF 2 vs XLIFF 1 1. XLIFF 1 was successful in controlled environments such as Oracle Translation Factory XLIFF 2 targets an open ecosystem of best of breed specialized tools
15
XLIFF 2 vs XLIFF 1 2. XLIFF 1 was intended as a “fire and die” format
XLIFF 2 is designed for a roundtrip among many tools Transfer only from System A to System B and back Each tool can provide its own specialized expertize work with different segmentation ignore optional features it doesn’t support
16
Microsoft and XLIFF 2.0 The Landscape The Problem The Solution
Multiple resource and file formats Multiple build and content management systems Multiple file transfer and localization tools The Problem High engineering cost Low visibility on status Bloated asset management The Solution A common interchange format A localization platform connecting producer and supplier Lean, agile localization
17
Common Interchange Format
4/30/2019 4:38 PM Common Interchange Format A Closer Look Build Resources LSBuild LCX Reach XLIFF CMS Documents XLIFF Utilities XLIFF LSBuild – MSFT proprietary build tool for software files LCX – MSFT proprietary XML schema for software files Reach – MSFT cloud based workflow system Suppliers can export XLF and use any industry standard XLF editor (current limitation for SW: binary data) © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
18
XLIFF 2.0 Specification Details Latest version of the specification
4/30/2019 4:38 PM XLIFF 2.0 Specification Core Modules Extensions Details Latest version of the specification Consistent requirements for implementation Required Core elements and attributes Optional Modules provide more functionality Extensible model through metadata and Extensions Core Translation Candidates Resource Data Resource Data Size and Length Restriction Size and Length Restriction Validation Validation Metadata Glossary Glossary Format Style Format Style Change Tracking Change Tracking Change Tracking Extensions Reach implemented Core, Metadata, and Translation Candidates to encapsulate Resource, Metadata, and Recycling information contained in Reach. We will provide an interface for other teams and possibly even suppliers to add their own modules and extensions Glossary does not meet the needs for complex Term Studio data so Reach implemented Metadata for terminology. Will look at future TBX mapping. Resource Data and Format Style implementation may be driven by future business needs Size and Length Restriction, Change Tracking, and Validation are not currently implemented since Reach has its own change tracking and validation mechanisms. These modules may have more application for supplier-side tools. © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
19
XLIFF 2.0 Infrastructure Components OM Utilities Reach MAT
4/30/2019 4:38 PM XLIFF 2.0 Infrastructure Components Object Model based on specification - Implemented as a PCL for cross-platform development Utilities to convert XML to XLIFF and XLIFF to XML Reach Workflows and Components OM Utilities Reach MAT Core Extractor Import Import Metadata Merger Export Export Translat. Candidates Validator Autotranslation OM Encoder/Decoder Extensibility OM OM=Object Mode, PCL=portable class library, MAT = multilingual app toolkit Utilities Extensibility: Customers can extended the Utilities to convert to and from and validate other formats besides xml. Reach Autotranslation: Recover ID shifts from extraction and provide MT. Reader/Writer OM Extensibility © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
20
Industry Adoption of XLIFF 2.0 Early adopters – SOU
Research Platforms SOLAS – CMS-L10N Industry Open Source – Okapi XLIFF 2.0 Tools – Bryan Schnabel’s XLIFF Roundtrip and DITA XLIFF Roundtrip tools Moravia ITS 2.0 XLIFF MT Roundtrip Web Service
21
Industry Adoption of XLIFF 2.0 Second Wave (working now)
Microsoft Lionbridge Multilizer XTM Ocelot
22
Industry Adoption of XLIFF 2.0 Third Wave (imminently upcoming)
Astoria Intel Kilgray SDL et al.
23
XLIFF 2.1 Approved Features: Planned Release Date ~October 2015
Advanced Validation Native support for ITS 2.0 Planned Release Date ~October 2015 Editor’s Draft
24
XLIFF 2.2 and beyond Requirements Gathering for XLIFF 2.2
6th XLIFF Symposium at 4th FEISGILTT at #LocWorld28 Berlin June 2-3, Cut off for 2.2 feature requirements in ~October 2015 Possible release Summer/Autumn 2016 XLIFF 2.x requirement gatherings at XLIFF Symposia Roughly 1 year release cycle
25
Questions and Answers Thanks a million for your attention
Thanks a million for your attention & &
26
XLIFF 2.x Resources I 6th XLIFF Symposium at 4th FEISGILTT at #LocWorld28 Berlin June 2-3, FEISGILTT Localisation Focus Volumes
27
XLIFF 2.x Resources II XLIFF 2.0 Standard (html authoritative)
CNGL blog on XLIFF 2.0
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.