Translation Workflow

Via the translation workflow, a translation of texts of exportable, multilingual and monolingual objects can also take place outside the object processing, e.g. through a translation agency. To do this, the object texts are exported automatically into XML files and imported again after translation. Fields are recorded in the translation file only if they can be managed in multilingual format (e.g. text fields, but no date fields).
Automatic changes, for instance to the identifier, are linked to the export and import. If an object text was exported, for example, the identifier is set to "In translation".

The translation workflow must initially be activated via the general system configuration.

Note:
If an object with the "In translation" identifier is to be edited again before importing the translation, then specific authorisation is needed, because changes lead to a new version of the object being created and the imported translation would only be found in the old version.

If a text has to be modified again after importing the translation, then the identifier of the object must be manually set to "Gap in translation" so that the object is taken into consideration during the next exporting process.

Translation Workflow Functions

In all managements in which exported objects are offered, advanced functions are available in the toolbar. In addition to functions needed for managing objects with several working languages, functions for exporting and importing object texts are also available.

Localisation -> Export gaps in translation

Texts of monolingual and multilingual objects can be exported for translation. With multilingual objects, the translation is imported directly into the source object. With monolingual objects, the object first has to be duplicated. A requirement for export is the existence of a base language and at least one further working language to be translated into. To do this, the identifier for this language must be set to "Gap in translation". After calling up the "Export gap in translation" function, all objects which were marked in the administration are exported. The export of subordinate elements, for example those which were assigned to the components tab in the course, can take place automatically. All files for an export process are stored in a previously specified folder as a ZIP file or downloaded directly via the interface. A log file indicates the successful export or delivers error messages. After export, the identifier is automatically set to "In translation". Editing can then be carried out only by certain users after confirming a warning message.

Localisation -> Import gaps in translation

The translated XML files can be imported both manually and automatically at a certain time. In the general system configuration, the time and folder in which the files are stored have been defined. In order to be able to import xml files, these must be packed into a zip file. The name of the zip file is irrelevant. The zip file must be stored in or uploaded to the import folder. Then, it is possible to click on any manager, e.g. courses or course templates on the “Import translations” icon on the toolbar. All objects which are marked as an xml file in the zip file are imported. Following successful import, the identifier is set to "Translated" and the object is displayed in this language in the learner's view.