1. Non-English Email Formats
By default, WIN‑911 encodes all outgoing email notifications according to ISO-8859-1. This ensures the best compatibility with legacy email clients. However, this encoding lacks support for many languages that are covered by UTF-8 in more modern email clients. This document will describe how to modify this encoding.
A. ISO-8859-1 Languages:
The following languages are fully covered by the ISO-8859-1 encoding:
|English (European and American)||Indonesian||Malay (Rumi script)||Rhaeto-Romanic||Swahili|
|Basque||Galician||Kurdish (Unified alphabet)||Norwegian (Bokmål and Nynorsk)||Scots||Tagalog|
|Corsican||Irish (modern)||Luxembourgish (basic orthography)||Portuguese (European and American)||Spanish (European and American)|
Some Latin alphabet languages have partial to near-complete coverage under ISO-8859-1; WIN-911 encourages users employing such languages to review the encoding details for their language to determine if their application employs any of the characters that would necessitate modifying the encoding. It may be easier to simply modify the encoding and test UTF-8 compatibility of all email clients (particularly for organizations that have standardized on one or two clients).
The following languages are partially covered:
It is important to note that users targeting languages lacking ISO-8895-1 coverage (including all languages not based on the Latin alphabet) should modify this encoding parameter to ensure that the alarm message reaches its recipient in a comprehensible form.
B. Modifying Encoding:
- Each WIN-911 Notifier format specifies an encoding in its XSLT syntax. Start by navigating to your Notifier Formats workspace (e.g. \Contact\Email\Formats) and opening the format for editing. NOTE: Click on the image to see an expanded view.
- Modify the first line of the XSLT by changing ISO-8859-1 to UTF-8.
- Next, modify the line specifying the <xsl:output by adding an encoding attribute set to UTF-8.
- Save the format.
- Repeat the steps above for each format you are utilizing in your configuration.
NOTE: HTML Email formats may still render incorrectly depending on your mail server and client; please utilize plain text formats in such cases.