Skip to content


Translation Manager

A translation manager is an Ibexa DXP user who will manage the process of translations. He will select content and translate content into target languages by exporting and importing XLIFF documents and interacting with professional translators and agencies.


An editor is an Ibexa Platform user who can create or edit content in the source language.


During its lifecycle a Collection will have a status, reflecting its current state. These are defined in the PHP class Xrow\TranslationBundle\Model\Collection.


Collections are exported from Ibexa DXP so that they can be sent to a Translator for processing.


A collection is exported as a ZIP Package containing the source texts in XLIFF format (one XLIFF file for each target language to be translated into). The exported package will be sent to a translator, who will return separate XLIFF files with added target translations, one for each language.

A Package is created from Ibexa through the Admin UI when new translation export job is created by clicking on the Start New Translation Export button.

The generated Package can then be downloaded from Ibexa through the Admin UI by clicking on the Download button.


A translator is a third party human or organization who uses translation tools like SDL Trados.

Translation Provider

A translation provider is a third party that receives untranslated content in XLIFF format from the Translation Manager, translates it, and sends translated content back to the Translation Manager for import into the Ibexa DXP content management system. There are two types of translation provider:

  • Manual, where a human user manually downloads untranslated Packages, and uploads translated XLIFF files.
  • Automatic, where a human user clicks on a Translate button to initiate an automatic transfer to and from a third party system, via some API.


Either an untranslated file containing source texts, formatting and other information in XLIFF format, or a translated file in XLIFF format containing source texts, translated target texts, formatting and other information.

XLIFF files have a structure corresponding to Ibexa DXP contents (<file> elements in XLIFF) and fields (<unit> elements in XLIFF).


Each translated XLIFF file completed by the Translator must be uploaded into Ibexa DXP. This is usually done through the Admin UI by clicking on the Upload button.


Once all the translated XLIFF files for a collection have been uploaded (one for each target language), the translations can be imported into Ibexa DXP through the Admin UI by clicking on the Import button.

This processes the XLIFF of each target language, and creates new translated versions of Ibexa DXP content from the supplied translations.

Last update: February 15, 2023