...

But you can add support for other languages quite easily by simply providing additional translation files.

Supported Languages are also defined in CoreOne Settings . SupportedCultures and DefaultCultures should be set accordingly.

Language Code Identifiers

In many places you will encounter that you either need to provide a two letter ISO code or a LCID for the language. The following table gives you a short overview of the most used languages:

You can find additional information on the following page: https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/63d3d639-7fd2-4afb-abbe-0d5b5551eef8

Localization files

If you would like to override any of the translations or even add a new language, you can add an appropriate localization file to the C:\ProgramData\itsense\LanguageData directory. In this directory you will find the itsense.moving.generated.xml which contains all default translations. Do not change that file. To change or add any of the translations, edit the appropriate override file.

For English this would be itsense.moving.en.overrides.xml, for German it’s itsense.moving.de.overrides.xml and so on. Within those files, you will find a simply key value list. The key is the translation key, and the value the appropriate translation. If you would like to change the default text for the validation message of the default uppercase rule, you simply change the entry as shown below:

Original file content, not containing an override:

{
  ...
  "Global.Validation.Password.Uppercase": null,
  ...
}  

Changed file content, containing a changed text:

{
  ...
  "Global.Validation.Password.Uppercase": "Please provide an uppercase letter",
  ...
}