With Multilingual Reactive Web and Mobile Apps you can translate an app to other languages. Once the translations are available in the app, you can switch the language automatically or let users do it.
Available in Platform Server 11.12.0 or later and up-to-date Service Studio.
When translating apps, note the following important information about language codes:
- The default language code is en-US.
- The current language is bound to the user session and when the user logs out, the language code automatically changes to the default language code.
- All language codes are in the RFC 1766 standard format.
- Language codes are case sensitive.
Here's how to get started:
- For instructions on how to translate your app directly in Service Studio, see Translate your app.
- If you want to extract text for sending it to a translation service, see Translation management.
- For instructions on how to translate older, Traditional Web Apps, see this section.
You can translate the following elements of your app:
- Screen titles
- Text in buttons, links, and screens
- Text literals in expressions
- Instructions in human activities
- Validation messages, widget confirmation messages, and empty state messages
- Static entities. Check Working with Static Entities for important notes.
Translating systems components
You can translate systems components. See the forum blog post System Components Translations for instructions.
You need to define at least one locale to be able to export the text resources from a system component.
Check out the Multi-Language in OutSystems training section for video resources and demos.
Articles in this Section
- Translate your app
- Translate your app directly from Service Studio by translating the module text and then creating a language switcher.
- Translating with the translation editor
- How to use the translation editor to translate your app in Service Studio.
- Translation management
- How to export text for translation and import back translated text.