The DITA XML file format is widely used for structured, topic-based authoring of technical content. Each .dita file typically represents a standalone topic, such as a concept, task, or reference, and follows the DITA specification defined by OASIS.

Transifex extracts translatable content from common DITA elements, including:

When a .dita file is uploaded, Transifex automatically detects and exposes for translation:

To protect certain strings, such as code samples, cross-references, or file paths, from being translated, you can use Smart tags in Transifex to "lock" those segments. Locked content is visible but not editable by translators, helping prevent accidental changes to technical elements.

Uploading a DITA XML translation file, the respecting parser will extract and match the content found in the file with the respecting content of the source DITA XML file, following the specific content order found on the source DITA XML file. Any differences in the structure of the elements between the two files will not allow uploading of the translation file.

When uploading a DITA XML translation file, the parser will go through each element identified and match translations to the source strings following the same order in the respecting source file. Please ensure the structure and content are relayed in the same order between source and translation files. Any difference will map the translations to different source strings.

The following table outlines what occurs to strings when using the API, CLI, or UI to manipulate translation files depending on download mode.