Translations
Translations
N2ACD-FE supports translating terms and phrases within the user interface of the application. Default translations are provided as part of the application however these can be overridden by creating unique branding configuration for a N2ACD FE deployment, and then providing translation files for this branding.
To deploy a custom translation for N2ACD-FE, the following steps must be taken:
- Create one or more translation JSON files.
- Configure the application to utilize the custom translation files.
Custom Translation
N2ACD-FE is a web application, built on standard web technologies including CSS, HTML and JavaScript. Translation in N2ACD FE primarily relies on applying a translation mapping file to the user interface, overriding the defaults.
A custom translation template can be found on the server hosting the FE interface at:
/usr/share/n2acd/floweditor-gui/gui/htdocs/i18n/en-gb.json
This may be used a starting point to adjust the user interface style. The left side of each key value pair represents the text or default value that is being replaced. The right side of the pair represents the value that is replacing the default value.
Web Server Configuration
Apache is configured on installation to serve all default translation files from http://host/n2acd-fe/i18n/, and this maps to the /usr/share/n2acd-fe/htdocs/i18n directory. Only an English translation file (en-gb.json) is currently used.
Each host’s branding configuration may contain its own translation file so they may be edited independently of one another.
N2ACD FE Service Configuration
Currently N2ACD FE only supports a single localisation file per configured host branding. Any changes that need to be made should be made to the en-gb.json file located in the relevant branding sub directory.