Web Management Console
Overview
Email Gateway Security supports translating its Web Management Console.
Currently the product is shipped with translations for British English (en-GB), US English (en-US) and Japanese (ja-JP).
Configuration
Email Gateway Security uses JSON format files to store the translation configurations and the actual translations for each supported language.
The configuration and translation files can be found in :
Default:
The configuration is done in the locales.json file.
Translation
New locales
Translation for a new locale may be created by duplicating and appropriately renaming an existing (e.g. en-US.json) translation file.
The new locale must be added to the locales.json file.
Changing existing translations
Translations for existing locales may be changed simply editing the appropriate translation file.
Editing translation files
The json format files are plain text files. Texts in these files may be edited using any plain text editor.
As an alternative translation file editor applications may be used, like:
- BabelEdit (proprietary): https://www.codeandweb.com/babeledit
- i18n Manager (freeware): https://www.electronjs.org/blog/i18n-updates
Product upgrades
Flags
Email Gateway Security has pre-installed the flags for most of the territories.
Flags that are missing from the collection may be added to <installation directory>\nginx\html\assets\img\flags (default C:\Program Files\OPSWAT\MetaDefender Email Security\nginx\html\assets\img\flags) in SVG format.
Not to translate or change
Notification, alert and report emails
Overview
Templates of the notification, alert and report emails can be found in:
Default:
These files are plain text xslt (Extensible Stylesheet Language Transformations) files, that can be edited using plain text editors or xslt editors.
Translation
The xslt template that belongs to the appropriate alert, notification or report email needs to be edited and the appropriate strings translated.
Subject translation
The Subject email header of notification, alert and report emails (also known as the subject of these emails) can be modified or translated by customizing the <title> attributes inside the <head> section in the appropriate xslt templates.
Conditional options
Content and/or subjects can also be translated/altered based on email classifications.
In the next example, the subject of a blocked notification can be different, depending on the classifications applied to the email.
Pre-translated content
Any additional pre-translated XSLT files can be found in sub-folders to the main xslt folder (<installation directory>\mailagenthost\xslt). To use these translations, copy the file(s) from the sub folder (for example, ja-JP) to the parent xslt folder.
Not to translate or change
Rendering
By altering the output format in the xslt template, the notification, alert or report email body format can be changed. This way the email client can be instructed whether it should render the email as HTML or plain text.
Supported xslt output values are html or text for HTML or plain text email bodies respectively.
For details about xslt templates see the Overview subsection of Notification, alert and report emails section above.
HTML email body
Set the following entry in the xslt template to get the notification, alert or report email body to be rendered as HTML:
<xsl:output method="html" indent="yes" />
Renders the notification email like:
Plain text email body
Set the following entry in the xslt template to get the notification, alert or report email body to be rendered as plain text:
<xsl:output method="text" />
Renders the notification email like: