Managing SigningHub Languages

By default, SigningHub comes with a full set of languages that are featured by language files, in JSON format, located at the installation path. Configurators can always manage these language files and may also modify these language files to change the language text as needed, considering they know what they are doing.

Language files location

[SigningHub's installation directory]\web\Scripts\app\languages\ [SigningHub's installation directory]\admin\Scripts\app\languages\ [SigningHub's installation directory]\api\Scripts\app\languages\ [SigningHub's installation directory]\mobile\Scripts\app\languages\ [SigningHub's installation directory]\core\Scripts\app\languages\

How are language files organised?

SigningHub maintains separate language files to manage localised content across different areas of the platform. These files cover translations for country names, time zones, signing reasons, and email templates, as well as settings for defining the default language in SigningHub Web, Admin, API, Mobile, and Core components.

Adding a new language

  1. From the language files location, go to the relevant folder.

  2. Open the "supported-languages.json" file in a text editor of your choice.

  3. Add a new key-value pair in the following format: "en-us": "English", where the "en-us" is the key, and "English" is the value.

  4. Save the file.

  5. Add a new JSON file to the current language folder.

  1. The file name must be unique and match the key. In case you are adding "en-us" language key in the supported-languages.json file, then the language folder must contain "en-us.json" file.

  2. SigningHub follows ISO 639-1 as the standard for universal language codes.

Deleting an existing language

  1. From the language files location, go to the relevant folder

  2. Delete the language file(s) from the folder

  3. Open the "supported-languages.json" file in a text editor of your choice.

  4. Remove the respective key-value pair from the file and save it.

  1. The deleted files will no longer be available for selection across the SigningHub deployment.

PreviousConfigurator NotesNextManaging Data Archiving

Last updated