XML alone does not solve the issue of global content

• To effectively leverage XML for global markets, you need to incorporate global information management

• You need a repository that can remember connections between source chunks and translated chunks

• You need a way to store translation assets at the sentence level and leverage them

• You need a way to manage terminology consistently

• You need to manage across multiple translation vendors and across a supply chain

• You need to track costs and reporting for managing global information

• You need to reduce mistakes in authoring terminology and writing standards

• You need to enforce standards for writing for global audiences

• You need templates that can handle layout in multiple languages

Think global from the start of your XML strategy

• SDL has experienced systems needing re-architecture because they were implemented with only one market and one language in mind

• For maximum ROI, take a strategic approach to the global dimension of XML

Automate the process of managing higher volumes of smaller chunks, being sent more frequently for translation

• XML promises to solve the problem of global content by reducing the amount of content that goes to translation

• It also introduces complexities, such as smaller chunks of content being sent for translation more frequently. Your CMS cannot handle this new complexity in translation but translation management systems can

Ensure translators can visualize the context of XML chunks

• Translating chunks of content is harder than chapters because the content is often out of context

• Terminology databases, translation memories and style guides all help the translator get a fuller picture of the chunk meaning

Optimize the structure of your XML for localization

• Taking heed of best practices on how best to prepare your XML content for localization will increase the efficiency of providing global content

• For example using variables presents a challenge for a translator where gender and word order are affected

• Different languages have different word order. If chunks are too small in English, they may not lend themselves to order change in target languages

Protect your XML code during localization

• XML code can get corrupted when sent to translators

• Apply technology to ensure your XML code is locked down and unbreakable during translation. If not, when your content is returned it will not load into your CMS or publishing engine

Ensure terminology and style are consistent across dispersed chunks

• When different authors are writing different chunks, terminology and style consistency can become harder to manage