DITAblogs (localizing)

How we made this document "localization-ready"

Currently there are no plans to translate this document into languages other than US English. However, it would be well positioned to do so for the following key reasons:

The document was written using DITA, an XML vocabulary well supported by popular translation tools.
We have put xml:lang attributes in all of our root elements.
The core vocabulary set could provide a translation center with basic information about the Toolkit and related products.
Most of the "about" topics have been "conref'ed" from the core vocabulary, so that content would need to be translated only once.

Preparing your DITA files to be localization-ready

Even if you have no immediate plans to translate your DITA project files into languages other than US English, you can make your projects localization-ready by:

Including xml:lang statements in your DITA source files.
Creating well-architected projects that make effective use of content reuse.
Always including a glossary, core vocabulary, or controlled vocabulary in your DITA projects.
Investigating translation technologies as you convert your legacy content to DITA, even if you have no immediate plans to translate, to be sure your DITA projects will operate effectively with popular localization applications.
Ensuring that your content management system integrates well with popular translation technologies.