Configure Interface Languages - Fluid Topics - 3.4 - Technical Notes

Manage Languages in Fluid Topics

Product
Fluid Topics
Fluid Topics Version
3.4
Category
Technical Notes
Target Audience
public

The language used for the interface of your Fluid Topics portal must be defined in the conf.json configuration file.

Edit the following file:

As antidot user

/usr/local/afs7/Fluid-Topics/conf/$TENANT_ID/conf.json

In the languages parameter of the ui object, add the ISO code of the desired UI language as in the following example:

{
  "ui": {
    "languages": [
      "de-DE",
      "en-US",
      "es-ES",
      "fr-FR",
      "it-IT",
      "ja-JP",
      "ko-KR",
      "pt-PT",
      "zh-CN",
      "zh-TW"
    ],
  ...
}

Any source content language code without a region designator falls back on its equivalent code with a regional extension, as listed in the mapping file.

Note: To see the list of default locales, use the Get Default Locale Configuration web service.
Note: A region-extended locale is the combination of an ISO 639-1 language code in lowercase and an ISO 3166-1 country code in uppercase, separated by a hyphen.
The first language entered in this list is considered as the default language and must be specified in all the parameters of the configuration file where a language must be entered, such as the following examples:
  • mainTitle
  • subTitle
  • metadata
  • footer
  • And so on
Note: This XML file is also used to manage the text of Fluid Topics email messages.