A Practical Guide to XLIFF 2.0 is structured to accommodate the diverse audiences that will use XLIFF and need to understand how to manage it effectively.
In Part I, âGetting Started,â we orient you to the OASIS XLIFF standard, describing how it works and how it fits into the translation process. We also describe its architecture, the difference between the XLIFF core and its modules, and the XLIFF conformance requirements. We recommend that everyone start by reading this section.
Beyond Part I, we recommend you focus on different parts of the book based on your role. Here are some typical roles and our recommendation for each.
Translation Architects: A translation architect is responsible for translations on behalf of a company, across departments, deliverables, and formats. This person owns the success or failure of the translation strategy. In this role, you are expected to know all aspects of the workflow, tools, schedules, roles, financial impacts, and technology stack.
If you are or wish to become a translation architect, you should read all four parts of this book.
Localization Coordinators: A localization coordinator is responsible for the translation of a specific workflow. This person coordinates the workflow with the Localization Service Provider (LSP), the content providers, and the publication stream and, in some cases, manages the budget for translations.
If you are or wish to become a localization coordinator, you should read all of Part I and the chapters that discuss the specific tasks for your role in Part II, âApplied XLIFF.â For example, if you are the localization coordinator for a web team, you should read Chapter 5, Translating Websites. In Part III, âXLIFF Core,â you should at least read the introductory material about XLIFF core features and functions. And in Part IV, âXLIFF Modules,â you should at least read the introductory material.
Technical Writers: Technical writers are often responsible for sending DITA and other XML-based content to translators without the assistance of localization coordinators.
If you are a technical writer, you should read all of Part I, and you should read the chapters that discuss the specific tasks for your role in Part II. For example, if you are a technical writer in a DITA publishing team, you should read Chapter 4, Translating DITA. In Part III, you should at least read the introductory material around XLIFF Core Features and Functions, and in Part IV, you should at least read the introductory material.
Localization Services Providers: Localization Service Providers (LSP) have a unique relationship with XLIFF. Computer-Aided Translation (CAT) tools generally use XLIFF as their native file format. And, more and more, informed translation customers send XLIFF to their LSPs instead of source content.
If you are a Localization Services Provider, you should read all of Part I, and you should read the specific tasks your customer is involved with in Part II. For example, if your customer is translating graphics, you should read Chapter 7, Translating Graphics. You should read all of Part III and Part IV.
CMS and other XML software developers: As a developer of content management systems (CMS) and XML software, you will need to know how to incorporate XLIFF into your publishing pipeline.
If you are a developer, you should read all of Part I, and you should read the the chapters that discuss the specific tasks your product handles in Part II. For example, if your platform is translating XML, you should read Chapter 3, Translating XML. You should read all of Part III, and in Part IV, you should read about any module that will enhance your translation workflow.
Consulting Groups: Consulting groups often want to incorporate XLIFF into the publishing pipelines they design for customers. If you are or wish to become a consultant, you should read the entire book.
Chapter 1. Introducing XLIFF
The need to provide information to people who speak a different language is an age-old challenge. The evolution of the tra...