Multilanguage Dictionary

In the Multilanguage Dictionary, you are able to add certain Symbols (specific Labels) with translations for every activated language in your application. Everywhere the Symbol is used, it will display the value according to the active Language. The available languages and the option to change language settings in your application, can be added to your user interface in the Project settings (see the Project Configuration documentation).

New Entries

Dictionary Entries (Symbols) can be added to by adding each translation item manually or through the import of a dictionary file. The dictionary can also be exported for outside editing and imported back in with a more complete dictionary. The 3 dots at the top of the dictionary list open the new entry menu in which you can choose between; adding an entry, Importing a file or export your dictionary.

Import

An import can be with either a xml file or a xlsx file with a set structure for the import. The file must consist of a column for the symbol or name, a parameter number and a column for each language.

Selecting the import options opens the dictionary import wizard, in which you can drop or select your dictionary file. Here you also select its behavior regarding missing languages and how to handle conflicts. These settings allow you to add languages through your dictionary import file and choose to either; override duplicates, ignore existing items or fail its import and return a error.

XML example:

<localization>
<entry symbol="ExampleSymbol" parameterCount="0">
<value culture="en-US">Example</value>
<value culture="nl-NL">Voorbeeld</value>
</entry>
<entry symbol="TranslationItem" parameterCount="0">
<value culture="en-US">Translation</value>
<value culture="nl-NL">Vertaling</value>
</entry>
</localization>

Excel Example:

Manually

The new dictionary entry should have a Symbol - a unique and recognizable Label Name, which can be used in Design Template Settings, in the Template Editor as Labels or in Expressions. For each available Language as defined in your Project Configuration, you can add the language-specific text to be displayed.

If you do not provide a Translation Value for a certain Language, the Symbol Name will be displayed in its place when that specific language is active in the Runtime.

The content of your dictionary can be used in the Template Editor as Label or in an Expression (used for displaying values), it will show in the Expression as "$Symbol" . You can also drag and drop the specific Dictionary Item onto the Template Editor Canvas or into the Expression Editor from the Dictionary Panel.

Depending on the active language, the specific translation value will be displayed in the runtime.

Dictionary Items can have one or more parameters, that you can position within the Translation Values using double curly brackets {{ and }} (creating placeholders). In the Expression where you want to use the Dictionary item, you can provide certain values to be replaced in those placeholders.

The translation for English is entered as: > The name "{{0}}" is not allowed. The expression on the Template is written as (using the LastName of the current user reference): > $InvalidName([Data.CurrentUser]->[Users.LastName]) The end result will be something like: > The name "NoNameEntered" is not allowed.

If the parameter is not provided, the expression will warn you that "an invalid number of parameters is provided", so you will have to provide a value for each placeholder that is defined with the Dictionary Symbol. If the value to replace the placeholder is empty, the display will just remove the placeholder and replace it with an empty string.

Import and Export

Release 4.2 (12-12-2024) features the much-requested Import and Export feature.

This option provides the way to import and export using either Excel or XML formats.

When the Import feature is used, options are provided to direct what to do with Languages which are in the File but not made available in the Project, and how to handle conflicts.

Add missing languages

If the file contains an entry for a language that is not made available in the current project, it will be automatically added to the project during import. This only applies to languages that are supported by the Modeler.

Conflict handling

A conflict means, there is an entry in both Project and in the Import file, and both instances have a value, but those values are different. An empty value in either instance does not cause a conflict.

• Override: the value from the import file will be used.

• Ignore: the value already existing in the project will remain (unless the value is empty).

• Fail: the import will stop and show an error for the conflicting situation.