Areas of language switching
The functions and definitions of the language switching system module are accessed at design time via the language switching node in the project explorer.
The language switching node has further sub-nodes that allow access to settings and definitions for language switching.
Configuration
This is where you define the languages for the localizable texts in your project.
User texts
Within the User texts node, you create the localizable texts that you require in the application and that are not functionally linked to other definitions from the project file.
Typical examples are
-
Labelling of buttons that trigger a function (OK, acknowledge alarm, save recipe, etc.)
-
Texts that are used in control elements that have no direct reference to the VisiWin system and are loaded programmatically into the control element
-
Text lists that are used in a control to switch the displayed text depending on a variable value
You can freely organise texts in text groups in the User texts node.
All texts in the nodes components, dialogues, variables, alarms etc. are referred to as system texts.
Components, dialogues
This contains texts that are used either as system messages or as internally linked texts in the control elements.
Variables, alarms, archives, user administration, logging, recipes
Many definitions from the other systems are implicitly assigned localizable texts as parameters. For example, if you define a new alarm, a localizable text is automatically created in the language switch. In the alarm editor, you have the option of entering an alarm text directly. This text ends up in the language switch in the associated localizable text as text in the developer language. The link between the alarm and text cannot be changed or deleted. The only task left to you is to organise the translation by either translating the texts in the language switcher yourself or exporting the texts using the translation managerin order to send them to a translation agency.