Click here to close now.


Industrial IoT Authors: Liz McMillan, Elizabeth White, Pat Romanski, Adrian Bridgwater, Tim Fujita-Yuhas

Related Topics: Industrial IoT

Industrial IoT: Article

What Is XLIFF and Why Should I Use It?

A brief overview of the XML Localization Interchange File Format (XLIFF)

Much time, energy, and commitment are required to develop and sell successful software products and Web-based services. Most products of this type are initially developed for a specific language and locale (e.g., U.S. English). To maximize return on investment, products can be customized so they may be available to the largest possible market - the global market. This customization process is known as localization.

Localization includes not only translation of the displayed text, but also adaptation of a product to comply with a country's cultural and legal practices. Examples of cultural conventions include date/time formats, postal address formats, font sizes, appropriateness of colors, numeric or currency formats and symbols, culturally appropriate icons or graphics, etc. The diversity of software platforms and technologies means that tools and technologies that support localization are also diverse and are frequently incompatible with each other. Industry standards drive process and technology efficiencies, and OASIS XLIFF (XML Localization Interchange File Format) has emerged as a standard interchange file format for localization-related data and metadata. This article will introduce the process of localization and summarize the challenges and issues facing those who localize. It will illustrate how XLIFF addresses many of the challenges and issues with descriptions of its architecture, provide examples of how to use it in real life, and discuss how it was developed and where it goes from here.

Localization: A Brief Overview
Having a product available in a different language increases the potential market into which it can be sold. Microsoft, IBM, and Oracle earn more than 60 percent of their sales from international markets. IBM recently reported that 70 percent of Web users speak a primary language other English. Within the United States, 18 percent of the population speak a language other than English at home. The Canadian Translation Bureau has reported that Canada represents 4 to 8 percent of the global translation services market with only 0.5 percent of the world's population.

The software localization industry was born in the mid 1980s as a result of the personal computer revolution. Early projects were very engineering intensive. Software developers would usually throw the final version of the application over the proverbial wall and expect the localization team to do the rest. The user interface and functional code were in the same file, which meant that functionality problems would often be introduced during the translation process. Before translation could begin, a software engineer would first need to change the character set code pages to ensure that software could be translated into the target language. Separating code from the UI required significant software development and localization resources. Physically and logically partitioning the UI data into separate resource containers reduced the severity and frequency of functionality defects introduced by the localization process.

The introduction of the Unicode character set standard and the growing emphasis on internationalization as a standard component of the software engineering practice was a very significant benefit to reducing the time and cost of localization. Internationalization is the process of developing software in such a way that it can run in different international environments without adapting or recompiling the code. Unicode introduced a common character set code page, and it is one of the corner-stones of software internationalization. The World Wide Web Consortium's (W3C) specifications and guidelines have addressed localization issues such as the separation of code and UI, character set issues, and date and time formatting. Cultural and economic factors are motivating many organizations to design and adapt their products for delivery to the global markets.

Today global markets are not content to wait months or even weeks for locally adapted software to be made available to them, so localization must now be done in parallel with the core product development. "Throwing software over the wall" to be localized after a product is sold is no longer an option.

The Internet introduces new challenges into the localization process by enabling more complex distribution models. Products and content are rolled out simultaneously throughout the global markets. The proliferation of diverse architectural frameworks and technologies upon which Internet and e-business applications are built has resulted in different degrees of complexity in both the core development and in localization.

Throughout its history, the localization industry addressed these business challenges through improvements in tools and processes delivered by competing vendors. Their solutions addressed specific technical or process requirements, but were rarely interoperable, which often resulted in vendor lock-in. With XLIFF, the localization industry got together to find a solution to some of the challenges that the industry is now facing.

Localization Challenges Addressed by XLIFF
XLIFF has already provided solutions to difficult localization challenges, including the following.

Challenge: Many different file formats to localize - The typical localization project is composed of data stored within many unique resource formats. Building tools to support the localization of these formats is costly and inefficient.

Solution: Transform or extract all localizable resources, regardless of native format, into XLIFF containers. For example, before XLIFF existed, one major database and enterprise software vendor localized 32 unique resource formats. Some of the formats were proprietary, others were legacy, but most were industry standards (i.e., Java List Resource and Property Resource Bundles, Windows RC Data, .html, .jsp, and various XML). Additionally, each new release introduced additional resource formats, usually XML-based, but each required extensive retooling of the localization tools, which lead to quality problems and scheduling delays. To reduce the retooling work and its consequences, the core development teams were given the responsibility of extracting or transforming the new resource formats to XLIFF before handing off for translation. Three years and three major releases later, the number of unique resource formats supported by the localization tools was reduced from 32 to a much more manageable 17. Additionally, by adopting XLIFF, the tools development team was able to shift resources that had been dedicated to retooling onto building new cost-saving enhancements such as XLIFF's built-in suggested translations features. Listing 1 is an example of a Java properties file and its XLIFF representation.

Challenge: Lack of version management metadata in native resource containers - Localization projects often run concurrently with core development projects, which means that resource files will be made of up of multiple versions or milestones. Version management at the segment level (a segment is the smallest discrete unit of translatable text) is a very useful feature if your goal is to maximize the reuse of previous translations. Web content is often dynamic, and multilingual content must be kept in sync in order to maintain quality. Few if any native resource containers provide a means of tracking the version of the content.

Solution: XLIFF provides metadata structures for tracking versions of source and translated content.

Challenge: Lack of workflow metadata in native resources - During the localization process, data passes through many different hands. Data to be localized is typically externalized by software publishers and handed off to a localization service provider, who in turn may hand it over to translation subcontractors. At each stage of the process, the types of data required are unique to the particular phase (source/target text, Translation Memory, Machine Translation, Termbase, etc.). Introducing automation into a development process saves money and resources and improves quality by ensuring the reproducibility of the process. Native resource files don't usually contain mechanisms for tracking the stage of the process at which changes were introduced to the localization process.

More Stories By Peter Reynolds

Peter Reynolds is manager of the software development team at the Dublin, Ireland office of Bowne Global Solutions (BGS), the leading provider of localization and translation solution. Peter and his team are responsible for developing some of the software that BGS use to run their business, including Elcano, the online translation service, and myInfoShare, the online project collaboration workspace. Peter has been working on XLIFF since its inception and is a founder member and secretary of the OASIS XLIFF Technical Committee. He also chairs the OASIS Translation Web Services Technical Committee.

More Stories By Tony Jewtushenko

Tony Jewtushenko is the founding and present chair of the XLIFF TC as well as the director of R&D for Product Innovator (, a Dublin, Ireland-based consultancy that provides product management, process improvement, localization, and internationalization services to software companies.
During his 23-year career, Tony was a key contributor to dozens of releases of successful commercial software products, including Lotus 1-2-3 and Notes, Oracle JDeveloper, and iDS. His multinational work and life experience spans USA, Europe, Middle East, and Asia.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@ThingsExpo Stories
The buzz continues for cloud, data analytics and the Internet of Things (IoT) and their collective impact across all industries. But a new conversation is emerging - how do companies use industry disruption and technology enablers to lead in markets undergoing change, uncertainty and ambiguity? Organizations of all sizes need to evolve and transform, often under massive pressure, as industry lines blur and merge and traditional business models are assaulted and turned upside down. In this new data-driven world, marketplaces reign supreme while interoperability, APIs and applications deliver un...
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
Electric power utilities face relentless pressure on their financial performance, and reducing distribution grid losses is one of the last untapped opportunities to meet their business goals. Combining IoT-enabled sensors and cloud-based data analytics, utilities now are able to find, quantify and reduce losses faster – and with a smaller IT footprint. Solutions exist using Internet-enabled sensors deployed temporarily at strategic locations within the distribution grid to measure actual line loads.
You have your devices and your data, but what about the rest of your Internet of Things story? Two popular classes of technologies that nicely handle the Big Data analytics for Internet of Things are Apache Hadoop and NoSQL. Hadoop is designed for parallelizing analytical work across many servers and is ideal for the massive data volumes you create with IoT devices. NoSQL databases such as Apache HBase are ideal for storing and retrieving IoT data as “time series data.”
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome,” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
Today air travel is a minefield of delays, hassles and customer disappointment. Airlines struggle to revitalize the experience. GE and M2Mi will demonstrate practical examples of how IoT solutions are helping airlines bring back personalization, reduce trip time and improve reliability. In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect with GE, and Dr. Sarah Cooper, M2Mi's VP Business Development and Engineering, will explore the IoT cloud-based platform technologies driving this change including privacy controls, data transparency and integration of real time context w...
The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, will explore the current state of IoT connectivity and review key trends and technology requirements that will drive the Internet of Things from hype to reality.
The IoT market is on track to hit $7.1 trillion in 2020. The reality is that only a handful of companies are ready for this massive demand. There are a lot of barriers, paint points, traps, and hidden roadblocks. How can we deal with these issues and challenges? The paradigm has changed. Old-style ad-hoc trial-and-error ways will certainly lead you to the dead end. What is mandatory is an overarching and adaptive approach to effectively handle the rapid changes and exponential growth.
Today’s connected world is moving from devices towards things, what this means is that by using increasingly low cost sensors embedded in devices we can create many new use cases. These span across use cases in cities, vehicles, home, offices, factories, retail environments, worksites, health, logistics, and health. These use cases rely on ubiquitous connectivity and generate massive amounts of data at scale. These technologies enable new business opportunities, ways to optimize and automate, along with new ways to engage with users.
The IoT is upon us, but today’s databases, built on 30-year-old math, require multiple platforms to create a single solution. Data demands of the IoT require Big Data systems that can handle ingest, transactions and analytics concurrently adapting to varied situations as they occur, with speed at scale. In his session at @ThingsExpo, Chad Jones, chief strategy officer at Deep Information Sciences, will look differently at IoT data so enterprises can fully leverage their IoT potential. He’ll share tips on how to speed up business initiatives, harness Big Data and remain one step ahead by apply...
There will be 20 billion IoT devices connected to the Internet soon. What if we could control these devices with our voice, mind, or gestures? What if we could teach these devices how to talk to each other? What if these devices could learn how to interact with us (and each other) to make our lives better? What if Jarvis was real? How can I gain these super powers? In his session at 17th Cloud Expo, Chris Matthieu, co-founder and CTO of Octoblu, will show you!
As a company adopts a DevOps approach to software development, what are key things that both the Dev and Ops side of the business must keep in mind to ensure effective continuous delivery? In his session at DevOps Summit, Mark Hydar, Head of DevOps, Ericsson TV Platforms, will share best practices and provide helpful tips for Ops teams to adopt an open line of communication with the development side of the house to ensure success between the two sides.
SYS-CON Events announced today that ProfitBricks, the provider of painless cloud infrastructure, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. ProfitBricks is the IaaS provider that offers a painless cloud experience for all IT users, with no learning curve. ProfitBricks boasts flexible cloud servers and networking, an integrated Data Center Designer tool for visual control over the cloud and the best price/performance value available. ProfitBricks was named one of the coolest Clo...
SYS-CON Events announced today that IBM Cloud Data Services has been named “Bronze Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. IBM Cloud Data Services offers a portfolio of integrated, best-of-breed cloud data services for developers focused on mobile computing and analytics use cases.
SYS-CON Events announced today that Sandy Carter, IBM General Manager Cloud Ecosystem and Developers, and a Social Business Evangelist, will keynote at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA.
Developing software for the Internet of Things (IoT) comes with its own set of challenges. Security, privacy, and unified standards are a few key issues. In addition, each IoT product is comprised of at least three separate application components: the software embedded in the device, the backend big-data service, and the mobile application for the end user's controls. Each component is developed by a different team, using different technologies and practices, and deployed to a different stack/target - this makes the integration of these separate pipelines and the coordination of software upd...
Mobile messaging has been a popular communication channel for more than 20 years. Finnish engineer Matti Makkonen invented the idea for SMS (Short Message Service) in 1984, making his vision a reality on December 3, 1992 by sending the first message ("Happy Christmas") from a PC to a cell phone. Since then, the technology has evolved immensely, from both a technology standpoint, and in our everyday uses for it. Originally used for person-to-person (P2P) communication, i.e., Sally sends a text message to Betty – mobile messaging now offers tremendous value to businesses for customer and empl...
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
WebRTC converts the entire network into a ubiquitous communications cloud thereby connecting anytime, anywhere through any point. In his session at WebRTC Summit,, Mark Castleman, EIR at Bell Labs and Head of Future X Labs, will discuss how the transformational nature of communications is achieved through the democratizing force of WebRTC. WebRTC is doing for voice what HTML did for web content.
The broad selection of hardware, the rapid evolution of operating systems and the time-to-market for mobile apps has been so rapid that new challenges for developers and engineers arise every day. Security, testing, hosting, and other metrics have to be considered through the process. In his session at Big Data Expo, Walter Maguire, Chief Field Technologist, HP Big Data Group, at Hewlett-Packard, will discuss the challenges faced by developers and a composite Big Data applications builder, focusing on how to help solve the problems that developers are continuously battling.