Bilingual XLIFF Files

One of the characteristics of XLIFF files is that they can be bilingual, i.e. they can contain both the source text and the translation. The translation does not need to be complete. For example, only individual source segments may be translated.

During check-in, the target-language content of bilingual XLIFF files is automatically inserted in the Target Editor of crossDesk.


The paragraphs prefilled in this way are set to the new editing state Touched (inserted from bilingual document) with the icn_cDesk_zustand_xliff_aus-zweisprachigem-dokument icon. Subsequently, the paragraphs may need to be edited by the translator and be set to the editing state Translated (inserted from bilingual document) with the icn_cDesk_uebersetzt-aus-zweisprachigem-dokument icon.


The target-language content of bilingual XLIFF files always has priority over the pre-translation in Across. Thus, a pre-translation will be performed only if the respective paragraph is not prefilled from the XLIFF file.

In the state-oriented view of crossView, prefilled paragraphs are presented separately under the category Inserted from Bilingual Document:


In the Across reports, pre-filled paragraphs are also presented separately in the category Inserted from bilingual document:


In certain application scenarios, it may be necessary not to adopt the target-language content of XLIFF files, e.g. if the XLIFF file to be translated originates from a content management system that has copied the source text to the target text for the export, in order to translate it as a normal XML document. In this case, it can be determined in the document settings templates of XLIFF that the target-language content is to be ignored during check-in and is not to be inserted in the Target Editor: