Example 3: Useing appwide language entries

If you want to use a general translation without need to use a prefix, you can define an app language.

Testausgaben:

To be replaced by name

To be replaced by doubleval

To be replaced by intval

To be replaced by boolval

VIEW-Requestor


<div id="translator_example2" swa="Translator FROM ../../../data/userinterface/translator/example1/translation_files.json"></div>

Output block


<p swac_lang="name">To be replaced by name</p>
<p swac_lang="doubleval">To be replaced by doubleval</p>
<p swac_lang="intval">To be replaced by intval</p>
<p swac_lang="boolval">To be replaced by boolval</p>

CONFIGURATION

There is no configuration needed.

DATASOURCE

The used translation_files.json defines the available translations. It contains one object for each translations. Each translation file is for one language and must contain the language code at the end of the file name.
The path is given as path from the app_root (this is configured in the configuration.js or automatically detected)

English translation file

German translation file