The first step in DITA localization is to translate the actual content of your DITA files. The second step is to address DITA localization requirements for your output. This article provides an in-depth explanation of the localization support in the DITA Open Toolkit.
Last month I posted about the five gotchas that will affect your translation turnaround time. That post focused on content quality, but I’d also mentioned how “a good LSP” would handle things. This month, let’s take a step back and look at five things that … Read More
Having worked at two translation companies and on many projects requiring localization, I appreciate just how nimble LSPs (language service providers) can be. Their ability to track down translators with the necessary subject matter expertise and handle a vast array of file formats is truly … Read More
In this webcast recording Bill Swallow, the manager of the GlobalScript division at LinguaLinx, discusses some of the ways you can cut your localization costs while still delivering quality content. Update 9/26/2014: Bill now works for Scriptorium.
Out of the box, the DITA Open Toolkit (OT) looks like it’s localization-ready. It handles the XML attribute xml:lang. It contains strings for more than 50 localizations. So it would seem that all you have to do is specify the language in your DITA files … Read More
The DITA Open Toolkit comes with support for many languages, but you can always find one that is not yet covered. Fortunately, adding a new language does not require any strange incantations.
STC Intercom, April 2009 A common argument for XML-based workflows is that they automate production and localization tasks. With XML, localization can be reduced to a fraction of its original cost, but how exactly does that happen? Sarah explores automization in localization and two technology … Read More