Translate XLIFF files with the file translation feature via the web translator, desktop apps, or API.
- When translating XLIFF files with DeepL, all texts stored in <source> elements will be considered for the translation.
- All <source> elements with a state attribute value other than initial or empty elements will be ignored for the translation.
- The translations will be placed in a <target> element and will be part of the same parent element <segment> as the respective <source> element. The translated file will contain the original source text and the translations.
- Units marked with the translate="no" attribute will be excluded from translation.
DeepL API Free and Pro subscribers can translate XLIFF files by using /document requests. Consult our API documentation to learn how to translate XLIFF files with the DeepL API.
XLIFF is a bilingual file format that is often used in the translation industry and stands for XML Localization Interchange File Format. It is based on the markup language XML.
XLIFF files contain both the original source text as well as its translation.
These texts are stored in the elements called <source> and <target>. The <source> element contains the original source text, while the translation is stored in the <target> element.
Both elements are child elements of a parent element called <segment>.
Troubleshooting
When translating XLIFF files with DeepL, <segment> elements will be considered for translation if
- the state attribute value is something other than initial or missing
- the <source> element contains text
The target language will be changed according to the selected target language in the translator.
If you choose another target language for XLIFF translation on DeepL than defined in the source XLIFF file, segments will be translated irrespective of their state attribute value. Also, the trgLang attribute in the translated XLIFF file will be updated accordingly.
For XLIFF version 2.0, comments and minor structural details might not be preserved after the translation. These include comments embedded between units, attribute ordering on inline elements and minor whitespace differences.