The DITA standard does not place limitations on what languages are supported. The only limitations are those placed by the tool or vendor you are using for DITA support.

One example of language support from tools is with generated text - for example, a caption that automatically begins with "Table #" before or after your table.

Another form of language support is in the actual translation of content - if you use a vendor to translate your content, then they will generally support translating to a specific set of languages.

Read more

Eliot Kimber suggested some low-cost (if not free) setups for DITA - and others commented on the dita-users mailing list.

A zero-cost option, with nothing to install, to get you familiar with editing DITA Topics and DITA Maps, is to join DITA Users. You use the browser-based DITA Storm editor or the desktop <oXygen/> XML editor with WebDAV access to author structured content in your own online workspace folder.

Read more

Stem sentences in technical communication have long been considered a standard practice to introduce new content, especially steps in a task. The task stem sentence, generally consisting of a partial sentence such as “To start the machine:” is not supported by any explicit DITA element in the DITA Task information type.

The question is: Should DITA include a stem sentence element in the Task information type?

[By the way, that was a stem sentence.]

Read more