Internationalization and localization
We can have internationalized and localized dashboards, and these are based on the i18n
jQuery plugin. When we need to translate a dashboard, we need to create multiple files in the same folder as the dashboard, all of the .properties
files.
The first one is messages_supported_languages.properties
, where we need to specify the languages that will be supported. This will dictate the files and languages that should be read. If we want to be able to provide transactions in Portuguese (pt
) and English (en
), we use:
pt en
Here we should have <language>
and/or <language>_<COUNTRY>
, where <language>
is the lowercase code for the language and <COUNTRY>
is the uppercase country code.
The i18n
properties files will be key/value pairs where the names will dictate the language that will be used. We can also make use of a fallback file, but the fallback file doesn't need to be defined in the supported languages file.
We can delegate i18n
...