Differences

This shows you the differences between two versions of the page.

--- 74:multilanguage [2019/10/25 11:23] – emr
+++ 74:multilanguage [2023/04/04 07:16] – [Limitations] mdht
@@ Line 1: / Line 1: @@
 ====== How to manage processes in multiple languages ======
-===== How to set up multiple language support =====
+Managing a process in multiple languages is an important asset when dealing with multilingual teams. It can also be used to translate standard processes for specific product lines that are developed by teams in a different language.
-Enable "Use multiple languages" at workspace
+===== How to enable multiple language support =====
+Support for multiple languages can be enabled at the respective workspace (Home > Administration > Workspaces > 3dot menu "Edit") where the process content is being stored.\\
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=74:74-translatesetup.png|{{  :74:74-translatesetup.png?direct&799x336  }}]]
+The workspace language will be used as the process default language.
+Elements that are not yet translated to a target language will be displayed in this default language. This also applies to search results. This allows to translate a process step by step while not yet translated content is still available to all process viewers independently of their language setting.
-Select desired language
 ===== How to manually translate =====
-Rename/Edit element names and descriptions
+To start translating process content, switch in your user profile to the target language to be translated to. As no translations exist yet, the process content will continue to be displayed in the default language.
-"Translate"
+All subsequent edits will be stored as the target language, e.g. renaming process element names or modifying descriptions. So to translate an element name from the default to the target language, simply use the ''Rename'' operation.
+{{  :74:74-rename.png?nolink&300x265  }}
+To see both the default and the target language side-by-side, use the ''Translate'' operation.
+{{  :74:74-translate.png?nolink&300x263  }}
+It results of both languages being displayed at the same time:
+{{  :74:sidebysidetranslate.png?direct&800x490  }}
 ===== How to automatically translate =====
-"Export for Translation" / "Import Translation" (How does this deal with elements that are already translated?)
+Whole process versions can be exported for automatic translation and re-imported afterwards. The details for both operations can be found here:
-Elements that are not yet translated to the desired language will be displayed in the workspace default language. This also applies to seach results. This allows to translate a process step by step while not yet translated content is still available to all process viewers independently of their language setting.
+  * [[:74:export_for_translation|]]
+  * [[:74:import_translation|]]
 ===== Limitations =====
-There are up to 5 languages in parallel supported per server.
+Up to 5 languages are supported in parallel. The list of possible target languages must be configured on the server.\\
+\\
+Available languages:\\
+language.de = German\\
+language.en = English\\
+language.fr = French\\
+language.pt = Portuguese\\
+language.es = Spanish\\
+language.it = Italian\\
+language.ru = Russian\\
+language.zh = Chinese\\
+language.ko = Korean\\
+language.ja = Japanese
+Add the configuration property “
+ <font inherit color: inherit; background-color: inherit /Courier New,Courier,monospace;;inherit;;inherit background-color: inherit >supported.languages</font>  ” in the config.xml and set its value to a comma separated list of required languages i.e. “
+ <font inherit color: inherit; background-color: inherit /Courier New,Courier,monospace;;inherit;;inherit background-color: inherit >en,de,ja,ko,zh</font>  ". Restart the Stages service.
 Managing association comments and string or text attributes in multiple languages is not supported yet.