Page History

Image Added

Localization User Interface

Enable Localization(Global Solution Setting)

Enabling this option allows these fields to be translated. For example, strings in Display will only be translated if 'Display Strings' is enabled, even if the string exists in the table.

Import Strings Wizard

Dictionaries

You can create multiple dictionaries and switch between them at runtime by simply setting the dictionary name.

Displays Localization Configuration Table

Configuring Display Localization

You can localize the text in your application in as many languages as needed. To do this, create a dictionary for each language. 

Language Switching Example

For an example on how to switch the language of a solution, check out Localization Solution. In summary, there are some things to look for when preparing your solution's localization:

1. Most of the components on display can be translated by changing the property @Client.Localization or using the method @Client.SetLocalization, as described above. If you want to translate just some strings but not all, you can use @Client.Locale method. For example, to localize a TextLabel component:
   Image Added

   Note
   When you enable Display Strings, you don't need to use the @Client.Locale method, all strings in the display will be automatically translated.

   
   

2. A dictionary named 'En_pt' was created with "Display strings" enabled. It translates the word 'Button' to 'Botão'. In the Task ClientStartup the following code is executed:

   Code Block
   @Client.Localization = "En_pt";

   In Draw, we have a button with the original Label Text 'Button'. However, since we used the dictionary and set a new language, it now displays 'Botão'.

3. Custom methods must be set up in order to localize components like ComboBoxes and DataTables. The Localization Solution page describes this process in detail

Reference Tags function in the same way as the tags being referenced, regardless of receiving different objects, different descriptions, and different enumeration sets. To ensure that the conversion will occur correctly in the FullDescription and ValueAsString properties, you must ensure that the Reference Tag is pointing to the desired object. You can use the syntax below in DisplayOpening in CodeBehind:

@Tag.<ReferenceTagName>.Link = @Tag.<TagName>.GetName();

In texts marked as Locatable in Symbols that are appearing in Dictionaries / Location, you should ensure that the texts are being passed for translation.

To add to the Dictionary the properties of all tags that can be associated with the reference tag being used in the display, follow the practical example.

Image Removed

If the reference tag is not automatically loaded in the Dictionary when clicking on the Locatable option and is not being translated from one language to another on the screen, follow the steps below:

1. Add the method Client.Locale(Tag.xxx) in the Expression field of your TextBlock to translate it to the current Client.Localization.

2. In the En_US dictionary, create one row for each TextBox you want to translate, containing the original text (in Spanish) and the translated text (in English).

This procedure should work for every reference tag you have in your solution.

Translate the column title of the DataGridWindow component

To translate the column title of the DataGrid component, it's important to note that this field does not have the locatable option and does not recognize Client.Locale() as a function. To translate column titles in a DataGrid, a script must be created.

The method below iterates through each column in the data grid and applies the @Client.Locale function to them. After the loop, the DataGrid is updated.

public void gridcolumntitle(){
        TDataGridWindow grid=this.CurrentDisplay.GetDataGrid("grid") as TDataGridWindow;
        foreach (GridColumn col in grid.Columns)
      {
       col.Title=@Client.Locale(col.Title);
       }
       grid.DoRefresh();
    }

To avoid overloading the client and maintain efficiency, the gridcolumntitle() method should only be called if the @Client.Localization has changed:

public void DisplayIsOpen()
{
	if(!@Client.Localization.Equals(aux))
	{
		gridcolumntitle();
		aux=@Client.Localization;
	}
}

Displays Localization Configuration Table

Property

Description

ID

Identifies each localization entry uniquely.

VersionID

Tracks the version of the localization entry.

OriginalText

Displays the original text before translation.

Disabled

Indicates if the localization entry is disabled.

TranslatedText

Shows the text after translation.

DateCreated

Records the creation date and time of the localization entry.

DateModified

Records the last modification date and time of the localization entry.

Description

In this section: