In, two components are distinguished for the language:

  • The system language (controls such as save button).
  • The content language

Multilingualism of the system language

German or English are offered as system languages. For a user, the system language depends on the language set in the browser:

  • If the language in the browser is set to German, appears in German.
  • If the language in the browser is set to another language, appears in English.

Emails are sent in the language of the initiating user.

The system language can be forced to German or English for in the configuration. This configuration will be adjusted by Model Aachen Support.

Multilingualism of the content language

The content of the appears in the inserted language. does not offer an automatic translation. However, there are plugins for the various browsers that offer automatic translation.

  • Caution: Using browser plugins for automatic translation can lead to serious display errors in

If the same content is to be displayed in different languages, the following ways are possible:

  • The managed translation.
    • The managed translation is recommended if the content in the different languages should not diverge over the revisions. The person responsible for the page should be able to bring in the offered languages himself. For implementation, the content in the additional language is added under the existing content. The different language blocks are marked with a heading (e.g. German / English) and the automatic table of contents is inserted at the beginning of the page. The person responsible for the page thus ensures the synchronization of the content within the scope of his approval.
  • The integrated translation
    • The integrated translation is recommended, if isolated contents are to be translated and thus a language predominates. Also, with this possibility, the side responsible person should be able to bring in all offered languages. If a content is to be offered in another language, it is added to an additional column of a table in the process description / work instruction.
  • The downstream translation
    • The downstream translation is recommended, if individual contents are translated into languages, which are not mastered by the side responsible persons themselves. Here, individual pages are created for each language offered and linked to each other (e.g.:"<link to the english process>" or "<Link zum deutschen Prozess>"). If a content is changed, the page owner has to make sure that the other page owners update their page as well. The does not support this process of downstream translation, because the effort and logistical problems involved contradict the basic principle of an interactive management system, with many small improvements.

Important: The described implementation options for inserting content in different languages are pure workarounds. These should be used if it concerns isolated contents and these contents must be created, e.g. from an external requirement (e.g. supplier audit). If a management system for practical guidance is to be set up for an international company with several sites, the MultiSite solution is recommended. This allows the principle of interactive management systems to be implemented across language barriers without effort being spent on often pointless and incorrect translations.

Translated with (free version)