Version 8.2 (2013-03-18)

Writing Multi Language Layouts

When defining properties of controls inside a layout definition, there are always two options to specify fix labels: either use property name or property textid. In case your pages support multi language ability, you only have to use the textid property. At runtime, the corresponding labels are found in the following way:

The following topics are covered below:


Example

Let us assume you have defined an application project "accountmgmt". Inside the application project, there is a layout definition account.xml that points via the translationreference property of PAGE to "account". The file structure inside your application project directory now looks as follows:

<webapp-directory>/
  accountmgmt/
    account.html                        // generated HTML file
    multilanguage/
      de/
        account.csv                     // German text
      en/
        account.csv                     // English text
    xml/
       account.xml                      // layout definition

Top of page

Page Name Strategy

The previous section explained how a translation file is found for a certain HTML page. Basically, the translation reference is used to link the layout definition and the Application Designer multi language management.

In general, there are two strategies for using this translation reference, and a mixture of both:

For larger projects, it makes sense to combine different literal information into one file - in order to keep consistency and to avoid redundancy. Of course, you have to synchronize the naming of text IDs for each page.

Top of page