Localization

The ‘Localisation’ menu node contains menu items relating to the management of localisations for the Lobster Data Platform.

For many texts (labels, messages, menu entries, etc.) within the Lobster Data Platform (especially for Lobster Data Platform / Orchestration functions), it is possible to assign a so-called localisation instead of the default text specified in the source code, which can be used to define a specific text for different output languages.

In all relevant cases, the ‘text resource’ in question is identified by a unique combination of two text values (Resource bundle, Resource name), which serves as a composite key for the assignment of localisations.

Text resources are often combined into a bundle for a specific object class. The fully qualified class name for the relevant class is then used as the text key for the Resource bundle, while the Resource name uniquely names the resource in the bundle. The name of the data field is used as the Resource name for the properties of an object. By convention, the Resource name $name identifies the resource that defines the localisation for the class name (see example in the screenshot).

The Localisation entries menu item opens a combined view that summarises information on text resources and their localisation in the list area, while the detail area allows you to edit localisations:

• In the screenshot, the list area (due to the text filter applied for the Resource bundle column: *.DateRange) shows all localisation entries for the bundle that concerns the ‘Date range’ class.
  
  

• The localisation for the DateRange class defines the selected line for the Resource name $name. The localisation for the supported Locale ‘German’ (de) is the text ‘Date range’ (see also German column and German text field in the detail area).
  
  

• The German, English and French columns show localisation values or the default text (not translated) if there is no localisation for a Locale.

• The Current column in the screenshot shows the same text as the German column. This is not surprising as long as ‘German’ (de) is selected as the Current locale.
  ►NOTE◄ The value for Current may differ from the value displayed for the Current locale if the State is ‘Changed’ (see below), Company specific localization is applicable or there is no localisation for the Current locale and therefore a localisation for another Locale is used.

• Flag columns whose title corresponds to the scheme Is <language> localised? use a symbol to indicate the languages for which localisations are available. This simplifies filtering or sorting the list.
  
  

• The Translations column indicates the number of languages for which localisations are available for the respective language management entry.
  ►NOTE◄ It is not necessary to explicitly store localisations for all languages. As a rule, the localisation for ‘English’ (en) applies as a fallback (see Locale for details).
  
  

• The State column is important for interpreting the information displayed in the list: