In this view you can define settings for a language available for modeling in QPR Modeling Client. To define settings for a new language, follow the steps below:
Define a name for the language into the Name field.
Define a unique language code for the language into the Language code field.
Provide an optional description for the language into the Description field.
Define a secondary language for the language with the Secondary language drop-down menu. The secondary language is used in the case translation is missing for some attribute. The secondary languages can be chained, i.e. language A can use language B as its secondary language, and language B can have language C as its secondary language. This means that in the case translation is missing for language A, language B is checked for translations, and in the case it does not have the corresponding translations, language C is checked. In the case the whole chain does not have translation for the text in question, the default language is used.
Define the Corresponding user interface language with the drop-down menu. The options available in the menu are languages found in the QPR Modeling Client dictionary. This setting affects flow chart images generated in QPR Portal (i.e. in the case there are Boolean values shown on the flow charts, values are displayed in the selected language) and does not have any effect in the QPR Modeling Client. In addition, this option does not link the Portal user interface language to the modeling language, i.e. both need to be changed separately regardless of this setting.
Note! The changes to language properties done in this dialog affect all the server models that use that language in multilingual modeling. That is, the settings on this dialog are server wide for that particular language.