Addressing localization issues with DITA and a CCMS

Products are sold into markets that cross both country and language boundaries, so the product documentation must be localized for the region where the products will be used. Localizing documentation is made considerably easier with DITA, a capable Component Content Management System (CCMS), and a Translation Management System (TMS). However, even with all the technology in place, you must still consider best practices and pitfalls!

When we look at typical events in the localization process (events for content and for content developers and managers), we see issues can occur as the content flows through content life cycles and flows across systems and organizations. A capable CCMS must be able to manage the issues that arise as well as manage the source language content and the localized foreign language content. Best practices are the key to avoiding pitfalls—and if the unforeseeable does occur, an understanding of the technology can go a long way towards crafting a workaround.

What can the audience expect to learn?

As Jim Tivy takes you through typical localization processes involving a DITA CCMS, you learn where issues can arise and how you can address these issues using best practices, technology, and on occasion a clever workaround. Jim addresses issues like determining which source content to send out, incremental localization, link management, and the relationship between managing localization and documentation releases.

Meet the presenter

Jim Tivy is CTO at Bluestream Content Solutions and a product architect of the XDocs CCMS. Jim has been designing software technology in the area of XML content for nearly twenty years. In 1999, he designed the first commercial XML database called XStreamDb and was a member of the W3C XQuery working group during that time. In 2005, Jim became involved with DITA as Bluestream added support for DITA to the XDocs CCMS. Since then, Jim has taken a lead role on further features of the XDocs CCMS and participates as a member of the OASIS DITA Technical Committee.

⇐Return to Agenda