Translations
Translations
N2FE 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 N2FE deployment, and then providing translation files for this branding.
To deploy a custom translation for N2FE, the following steps must be taken:
- Create one or more translation JSON files.
- Configure the application to utilize the custom translation files.
Custom Translation
N2FE is a web application, built on standard web technologies including CSS, HTML and JavaScript. Translation in N2FE primarily relies on applying a translation mapping file to the user interface, overriding the defaults.
A custom translation template is included at the bottom of this page. This may be used a starting point to adjust the user interface style.
Web Server Configuration
Apache is configured on installation to serve all default
translation files from http://host/n2fe/i18n/, and this maps to the /usr/share/n2fe/htdocs/i18n
directory. Only an english translation file (en-gb.json) is currently used.
Each host branding configuration may contain its own translation file so they may be edited independently of one another.
N2FE Service Configuration
Currently N2FE 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.
Custom Translation Template
The following custom Translation template can be used as a baseline for translating the N2FE user interface. 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.
All values defined within the template file are all the currently supported replacements.