Next revision | Previous revision |
710:configure-languages [2024/03/06 01:32] – created - external edit 127.0.0.1 | 710:configure-languages [2024/09/26 19:15] (current) – Meier, Erich |
---|
====== Configure additional languages ====== | ====== Default and additional languages ====== |
| |
Stages comes with English, German and Chinese translations. Other languages can be added in the following way: | Stages supports the following languages by default: **English, German, Chinese, Japanese**. |
| |
- Edit conf/config.xml and add/edit the following property by adding the additional language, e.g. "ja" (for Japanese): \\ ''<property name="supported.languages" value="en,de,zh,ko,**ja**"/>'' | Additional languages can be added in the following way: |
- Execute bin/update.bat (Windows) or bin/update.sh (Linux). \\ This will generate a properties file with the suffix of the new language (e.g. **stages_ja**.properties) in …\stages\data-cache\generated. The file contains the English translations. Do not modify it directly because all changes will be overwritten by the next execution of update.bat/sh. | |
| - Edit conf/config.xml and add/edit the following property by adding the additional language, e.g. "eo" (for Esperanto): \\ ''<property name="supported.languages" value="en,de,zh,ja,**eo**"/>''**//WARNING: new languages always need to be added at the end of the list. The list should not be reordered, otherwise already modeled process content will show in the wrong language.//** |
| - Execute bin/update.bat (Windows) or bin/update.sh (Linux). \\ This will generate a properties file with the suffix of the new language (e.g. **stages_eo**.properties) in …\stages\data-cache\generated. The file contains the English translations. Do not modify it directly because all changes will be overwritten by the next execution of update.bat/sh. |
- Do the desired translations: | - Do the desired translations: |
* Go to conf folder and create a new file there as a copy of local.properties. It should be named local_[enter language abbreviation here].properties. Example: **local_ja**.properties. | * Go to conf folder and create a new file there as a copy of local.properties. It should be named local_[enter language abbreviation here].properties. Example: **local_eo**.properties. |
* Copy all message properties that you want to translate from the file that was generated in step 2 | * Copy all message properties that you want to translate from the file that was generated in step 2 |
* Paste the message properties to the new properties file in the conf folder and translate the message texts there | * Paste the message properties to the new properties file in the conf folder and translate the message texts there |
- Execute bin/update.bat (Windows) or bin/update.sh (Linux) again. | - Execute bin/update.bat (Windows) or bin/update.sh (Linux) again. |
- Restart Stages. | - Restart Stages. |