Global Content Management Solutions-Localization Engineering of Global Content
Throughout the many years in which I’ve been professionally involved in the field of Localization Engineering, I can’t remember how many times I’ve been asked the question, “so, what exactly is it that you do again?” Some of my closest friends have stopped trying to understand…
For some, the term evokes certain expectations based on the role of traditional software engineering, and in the context of a software localization project, one may understandably ask the question, “My product has already been engineered, why is localization engineering necessary? Don’t I just need translation?”
I hope the following explanation will help clarify the role of Localization Engineering and help you to obtain the maximum benefit from this function.
The Localization Engagement
The professional translation industry is in many ways a world unto itself, comprised of its own unique characters, history, practices, pricing paradigms, expectations and idiosyncrasies. In a word, it has a culture. When a company developing a globally-targeted product engages in business with the translation world, it brings to the table its own culture, and more often than not – unique requirements.
Localization services (like those provided by Lionbridge) focus on this intersecting space between a company’s language needs and the services provided by the translation world, an area that I call the “localization engagement.” The primary mission of the localization engagement is to make sure that the company’s requirements for language-related services are satisfied.
Like snowflakes, localization engagements are unique – coming in as many different shapes and sizes as there are different kinds of customers. From a technical standpoint, each localization engagement can bring with it a unique set of logistics that must be successfully managed. This is where Localization Engineering kicks in.
Logistics, Logistics, Logistics
There are some logistics which are are common to most localization engagements: Content that is targeted for translation must make it into the hands of translators in a format in which they can do their work using CAT (computer assisted translation) Tools, such as translation memory and online glossaries (a process typically called “pre-processing”). After translation, said content must be converted, in translated form, back into the format from which it originated (this is typically called “post-processing”).
Here’s an example: Let’s say that we have a single English html file that needs to be translated into French and Japanese. That file would be converted into a format that works with the translation tool we’ll be using across the project – let’s say XLIFF. The process of conversion involves a parsing step which chunks-up the file into categories of content, most importantly translatable content and non-translatable content (such as the html code itself).
The XLIFF file is distributed to French and Japanese translators who return the XLIFF in bilingual format. The bilingual files are then rendered back into their native html format, but with all English UI now in French and Japanese.
Sounds simple enough, but with the huge variety of software types, publishing formats, and other forms of content – each with different syntax rules, content length restrictions, levels of support for encoding, techniques for storing translatable text, etc. - there are actually lots of details to address. Now multiply these logistical considerations with those that originate on the translation side: different character sets, behavior of translation tools, translator operating environments, linguistic rules, etc. and things can start to get complex, even on a “straightforward translation project.”
Add the additional activities of synchronizing updates, testing localized content, and (choke) modifying formatting to accommodate the inevitable text-expansion, and the oversight of an expert becomes important. The Localization Engineer is that expert. It is his/her job to make sure that these logistics are taken care of.
If you’ve engaged in localization before and have never experienced corrupted text, broken code, untranslated content, the manifestation of post-translation functional issues, or user interface that just doesn’t seem to make sense anymore, that’s great! It means that the Localization Engineering function was performing as intended.
Invoking the Innovator
While managing technical logistics at the project level is important and necessary, the true power of the Localization Engineering function is realized when it is applied at a higher level. That is, the more you can involve such an expert in your overall plans and give them visibility into the processes and requirements within the “blue circle” of your global endeavors, the more that person will be able to develop the most streamlined, cost-effective, and risk-proof engagement strategy possible for you. Involve them early, and hold them accountable for constant improvements; that’s what engineers do best!
Lionbridge has the good fortune of having many of the best and most experienced Localization Engineers in the industry. If you want to put their expertise to work for you, give us a call.
As always, your feedback is encouraged and appreciated!
