You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Blueriq allows you to implement multiple languages and dialects in a single application.
Defining Languages and Dialects
To support multiple languages, you first define the language at the project level. You can also specify a dialect, such as formal or informal, if you want to adjust the tone of voice in your application for different user groups.
Additionally, you need to select the default language for your model.
This setup can be configured in the "Languages" tab located in the project properties panel (see the image on the right for reference).
Modeling a multilingual application
Once your project languages are defined, you can start setting content for each language. In Blueriq Encore, fields that have a multi-language icon (
) allow you to define content in multiple languages..
These fields can include:
- Display names for pages and containers
- Question and explanation texts
- Documents
- Content items
- Text items
- Value list items
- And more...
An indicator next to a field shows how many additional language definitions exist for that particular field.
The switch in the titlebar of a view (
) can be used to set all language fields within a view to another language.
Running a multilingual application
In the development dashboard’s flow starter, you can select the project language with which you want to start an exposed flow of an application. This selector adds the language code (e.g., languageCode=nl-NL) to the URL, specifying the desired language for the flow.
In a production environment, you’ll likely use shortcuts to start the application. These shortcuts also include the language code.
If your model uses one of the decoupling patterns, such as external flow or AQ_StartProject, keep in mind that the language selected to start the main application will apply to all decoupled elements within the application. However, if you want part of your application to use a different language, this can be achieved by implementing a custom plugin, such as a container-type or service-type plugin.
Overview
Content Tools