Languages in Novulo: how does it work and how to overrule

Novulo applications can be used in multiple languages.

In your log-in screen, you can choose between the languages available for your application.

image

The languages displayed depend on the composition and configuration of your application. Also, as you can see, it’s a “culture”, as it’s not just a language but also a country that defines the settings.

The Language + Country togehter (“culture”) define the language of all menu’s and buttons, but also the formatting of Dates and Numbers.

Especially in English, this makes a significant difference.

In US English, it would say
4/11/2024 3:27 PM for 11 April 2024.

In English (United Kingdom) it would say:
11/4/2024 15:27 for 11 April 2024.

Also, the thousands and decimal separators differ.

How are the languages and cultures defined
For the languages, by default, all languages that are supported by all components in your application are displayed.

If your application has many components that support English and Dutch, but one component is in English only, the Dutch choice will be removed automatically.

For the countries, it selects the countries available on your server for that specific language.

It is possible to explicitly define the cultures you want to support with a web.config key. This will overrule the automatatically determined languages.

If you add the following to your web.config, your application will offer English (US and GB) and Dutch (NL and BE), irrespective of your component selection.

<add key="languages" value="en-GB;nl-NL;nl-BE" />

This can be done using the Custom Web.Config settings in Deployment.

It can be used both to disable languages you don’t want to show, as well as to force showing languages that are not fully supported.

When you log-in with a language not fully supported:
a) It will fall back to English in all forms, panels and grids
b) It will (3.8 platform) show empty texts in the Column Selector as well as dropdowns to select fields like in the export engine. (a request to always fall back to English is submitted for 3.9 but not yet confirmed ATM).

2 Likes

Alternative way to change the culture and language within the session (even when the log-in screen dropdown, does not support the language defined in the webconfig) is after logging in to append a query parameter to the url ?language={culture-string-here}
For example, in this application, nl-NL and dutch languageis not selectable in the login screen:


It is recommended that it is configured as explained above and if you want specific language and culture to include it in the webconfig, however for quickly testing something without doing application update you can do (after logging in):
?language=nl-NL
Now my application session runs in Dutch with Dutch culture:

2 Likes