Multi Language Handling

You can display and edit texts of a solution not only in the primary content language but also in secondary content languages. You can also translate texts from any language to any other. This is possible for the Solution Documentation structure and diagram element names and descriptions. However, note that Knowledge Warehouse documents do not support this function.

In Solution Administration, the available content languages in a solution are displayed on the Properties tab in the area Solution Settings.

In Solution Documentation, a language selector is visible in the header if more than one language is available. The content language does not change when you change the branch as the content language is solution-specific.

All tool texts (header texts, buttons, link texts, menus, labels) are displayed in logon language.

All structure elements, assignment names, some value helps on external objects, some attribute values and diagram entity names and descriptions are displayed in the selected content language, if available. For some value helps and attribute values the logon language is used.

All structure elements, assignments and diagram entity names and descriptions are tagged with their fallback language in brackets as suffix, if they are not available in the selected content language. The fallback language is determined by the sequence of content languages. Example: If the fallback language is English, texts should have (EN) at the end. This information is visible in the browser, list, search result, where used list, reporting, process document, attributes panel, and in diagrams.

Activities

Add Languages

In solution administration, select the Properties tab. Select the Edit-link at the field Content Languages. The systems opens a dialog on which you can add further content languages from a list of installed languages. You can sort them in the sequence in which you prefer to read texts. You cannot remove the primary content language from the first line because this language is fix and determined when you created the solution. In Solution Documentation, the content languages of a solution are displayed in the same sequence as maintained in solution administration.

Translation

Select a content language different to the primary content language and different to the logon language with the language selector. Select a structure item and translate it into the content language simply by removing the language suffix and changing the name. All changed names and descriptions of structure items are saved in the selected content language. The language suffix disappears.

Open a diagram and translate some diagram entities into the content language by changing their name. All names and descriptions of diagram entities are saved in the selected content language.

If you create new structure elements and diagram entities, the default names for new structure elements are in the current selected content language.

Use of Translation Mode for missing translation

You can activate the Translation Mode by choosing the following function in the menu: Start of the navigation path Global Functions Next navigation step Settings General Translation Mode End of the navigation path . As a result, all language dependent texts in browser, diagram and attribute pane that do not exist in current content language are displayed in red color. On mouse-over of a colored text a quick-info shows the information Translation missing.

Copy of elements in different content languages, e.g. a scenario with processes

If you copy elements in different content languages, as an example a scenario with processes, all languages are copied as well. If texts are not available in the content language, a fallback language is available for every text. The copied structure element itself (in our example the scenario) is created only in content language. No fallback texts are copied since the copied structure element is typically renamed after copying. If the structure element is not available in the content language a fallback language is used.

Use of Lifecycle operations and different Languages

If you use lifecycle operations like Release, Revert, Mark Conflict as resolved on structure elements in multiple languages, all available languages are released or reverted in these operations. Only changes in the primary content language are regarded as conflicts. Changes in other content languages never cause a conflict. However, you should release every text change in any of the content languages regardless of the selected and visible content language.

Reset of Content Language and Translation Mode to default

If you want to reset the current content language to the primary content language of the solution and switch off the translation mode choose the following function in the menu: Start of the navigation path Global Functions Next navigation step Settings Reset Settings Reset to default End of the navigation path .