Two of the key reasons organizations cite for using DITA are:
Localizing DITA content consists of two steps:
For example, the "Contents" label that appears above the list of contents on the first page of a PDF2 output file, as shown in the following figure.
Another example would be the "Parent topic" and "Related topic" labels that appear in XHTML output files, as shown in the following figure.
The translation of these generated strings are controlled within the Toolkit build process.
An example of DITA content is the string "You can save money by buying produce when it is season." string in the figures above.
The translation of the DITA content is done (usually handled by translation centers or done by individual translators) outside the Toolkit build process.
DITA and DITA Open Toolkit support the languages listed in the following table.