Languages
Content objects can be managed in one or more languages.
Multilingual Administration
If content objects are maintained in multiple languages, learners can select the language in which the content is displayed to them.
Multilingual content objects
The languages are managed in the multilingual objects on a separate language tab. Any number of implementation languages can be added and removed there. Which languages are available in total is specified via the general system configuration.
When creating and editing multilingual objects, a distinction is made between:
Administrative Language
The administrative language is used when managing objects. This language is defined in all tables and info areas irrespective of how the object is displayed to learners later on.Base Language
The base language is used as the basis for a translation.Alternative Language
When learners open an object which is not available in their preferred language, the object is opened in the alternative language. It is recommended to select an alternative language that has been mastered by most learners.
The translation status is labelled for each language. This status is set manually or, if the translation workflow is activated, is assigned automatically when the object texts are exported and imported. There is an identification of the translation status for each language. This status is set manually, or - with activated translation workflow - assigned automatically when exporting and importing object texts.
Do not translate
If an object is already prepared in terms of content but not yet ready to be finally published and used, the identifier can be set to "Do not translate". This indicates to a translator that the object does not yet exist in its final state and that a translation is not yet necessary. The language cannot yet be selected by the learner and is not taken into consideration during automatic export of the text to be translated.Gap in Translation
If an object is available in a language that has not yet been translated the language is marked automatically as a gap in translation. If the translation workflow is active, the object text for the language which is marked as a gap in translation can be exported. After successful export, the identifier is automatically set to "In translation". The language is not yet made available to learners.In Translation
If an object is currently being translated this can take place in several sub-steps. A translator can change the status to "In translation" manually. If the translation flow is active, the identifier is set automatically as soon as the object has been exported. Languages which have this identifier are not yet displayed to learners.Translated
If the final translation exists and can be made available to learners, then the identifier must be set to "Translated". If the course was already available to learners in other languages, the language whose identifier was changed to "Translated" will now be displayed as well.
WBT (SCORM)
Learning content of the type WBT (SCORM) is a special case. The languages available for these objects on the language tab are controlled exclusively via the manifest file, which is part of the imported ZIP file. To create a multilingual SCORM WBT, the same languages must be defined in the manifest file for the WBT and all its sub-objects (SCOs) for all fields used. A separate localisation function is available for updating the languages and the language-dependent description texts (see below), which allows the ZIP file to be uploaded again after changes have been made to the manifest file. This function is used for WBT (SCORM) instead of the translation workflow used to translate other multilingual objects. As learning content of the type WBT (SCORM) is not exported for translation, there is also no base language here. It is therefore only necessary to define which of the languages used is to be used as the administrative language and which is to be used as the replacement language. For both purposes, the language defined first in the manifest file is preselected. As the translation of SCORM WBTs takes place entirely outside the learning platform, the managed languages are always labelled "Translated". The localisation functions described below are therefore limited for SCORM WBTs.
Monolingual Administration
For multilingual courses, it is advisable to also provide their learning content, tests and feedback in multiple languages. For some learning content, however, a multilingual display for learners does not make sense, as a standardised communication language is required, e.g. for forums. In this case, a separate forum should be integrated for each course language.
Functions in the Management of Content Objects with Multiple Execution Languages
Language Management
The "Language management" function can be used to add or remove languages for individual objects and to change the administrative language, base language and replacement language. In addition, the labelling for translation can be implemented for each language. These settings are also possible on the language tabs of the respective objects. In contrast, the "Language management" function does not create a new version of the object when changes are saved, which makes it easier to make changes to objects that are already in use.
Add Languages
If languages are to be added to several objects at once, this can be done using the "Add languages" function. Languages that are already present in all objects are displayed normally, languages that are not present in all but at least one object are displayed with a dashed border. This language can be selected again when it is added. The additionally added language is added to all objects selected in the administration that do not yet have this language and marked with the label "Translation gap".
Change Basis
If a different source language is to be selected as the basis for the translation, this is possible for several objects at once using the "Change basis" function. Only the languages that are available in all selected objects and are also labelled as "Translated" are displayed in the selection.
Change Default Language
The alternative language of an object is always displayed to the learner if the preferred implementation language is not available. Only the languages that are available in all selected objects and are also labelled as "Translated" are displayed in the selection.
Identification
Several objects can be selected to change the labelling. All languages of all selected objects are listed. If the labelling for a language, e.g. Translated, is the same in all objects, this is displayed. If a language has different labels in the selected objects, the input field is displayed empty. By setting a new label, this is transferred to all previously selected objects.
Language Dependent Files and Links
Various content objects have uploaded files or references to other objects, which may also need to be available in several languages. A separate file can be uploaded for all languages of the object without creating a new version of the object. The function can be used for the following objects and fields:
Tests and test templates: Offline layout
Feedback and feedback templates: Offline layout
Test questions and feedback questions: Media file upload
Courses, course templates, learning paths and learning content: File upload, link (URL), source (URL), certificate of participation in case of failure, certificate for successful completion. The input fields mentioned must be integrated as meta tags in the respective objects.
WBT (SCORM) Language and Text Update
This function is used to add or remove languages to a WBT (SCORM) and to update the language-dependent descriptive texts of the object. To do this, the modified source file of the WBT is uploaded, similar to uploading a new WBT. In contrast to the WBT content update, where only the WBT content is re-imported (see Learning content), only the languages and language-dependent description texts defined in the manifest file are updated. As no new version of the learning content is generated during this process, the changes are immediately available, e.g. in courses in which the most recently published version of the WBT has already been added. This makes it easy to add new languages to SCORM WBTs that are already in use on the learning platform. If the content of the WBT is not yet available in the new languages, the content must also be updated. No new version is created for this either.