To add a locale, perform the following steps.
Edit the uwcdomainconfig.properties file. This file is available in the <uwc-deployed-path>/WEB-INF/domain directory>
Add a keyword for the new locale that needs to be added. For example, if you need to add a new locale, “Afrikaans”
supportedLanguages=en;es;de;fr;ja;ko;zh-CN;zh-TW;Afrikaans |
Add a localized string for the locale name in different locales. This could be done by adding a new line in i18n.properties file of each locale. For example, let us add a key in i18n.properties file for en locale.
uwc-common-options-preferredLanguage-Afrikaans=Afrkaans Locale |
Some mail clients do not set the encoding type in MIME header before sending emails. Communications Express allows users to view a message in a different character encoding.
For example, Arabic has a number of character encoding (CP-1256, Arabic DOS, UTF8, Nafitha, Sakhr, ISO-8859, MacArabic). Communications Express allows users to change the browser encoding to be able to view the mail that they receive in different character encoding.
Change directory to <uwc-deployed-path>/webmail/ directory.
Edit main.js and uncomment the following line:
//var srcchars = new Array('standard','iso-8859-6','windows-1256', 'utf-8','big5','gb2312');
You can also add or remove character encoding that you want to support in the Array data type. For example:
var srcchars = new Array('standard','iso-8859-6','windows-1256','big5','gb2312', 'windows-1252','iso-8859-7');
Restart the web container on which Communications Express is deployed for these changes to take effect.
Users need to clear the browser cache so that the latest modifications made to the main.js file are picked up from the server instead of the browser's cache.
For multi-tier deployments, these steps should be performed in the front end directory (<uwc-deployed-path>/webmail/) of the Communications Express installation.