Any application is designed using a particular language called the default language. It is in this language that the application is executed by default, however, you may have your application translated and executed in other languages, that is, a multilingual application.

Adding Other Languages

In the eSpace tree, under the Multilingual Locales folder, you have listed all languages for which your eSpace has translations and is where you are allowed to add other languages.

Translatable Resources

In your eSpace, all elements that can be translated, such as, the text in Text widgets or the labels of Button widgets, are called Translatable Resources.

Translation Process

The translation of your eSpace is made exporting the translatable resources to files which are sent to the translator. After the translation job is done, the files are imported back into your eSpace and translations updated. Learn more about the Translation Process.

Language Built-in Tools

You may operate with the language locales (String that uniquely identifies the language as specified in RFC 1766 standard.) to, for example, change the language in which your application is running or display the current language of your application to the end-user, using the Language Built-in Tools.

Restricting the Translatable Resources

To improve your translation process you may select which translatable resources are effectively to be translated and which aren't using the Translations Behavior Editor.

You may also edit the translated texts in the Translation Behavior Editor.

See Also

Adding Other Languages | Translatable Resources | Translation Process | Language Built-in Tools | Translation Behavior Editor