Chapter 10 Localizing Communications Express

Communications Express allows you to localize Calendar, Address Book and Options as per your requirements.

Localizing Calendar and Options

To localize text, you need to change i18n.properties file that is deployed in <domain-dir>/domain. The i18n.properties file in <domain-dir>/domain is the default file. If the deployment is configured to work with multiple domains and multiple locales, then a directory by that domain name is created under <domain-dir>/domain

For example, if there is a domain called example.com, perform the following steps.

Create <domain-dir>/domain/example.com

Copy <domain-dir>/domain/i18n.properties to <domain-dir>/domain/example.com. This would be the defaulti18n.properties for users in example.com domain.

Create directories for each supported locale (en_US, ja, de_FR etc) under that domain, copy i18n.properties to the domain, and change it accordingly

The i18n.properties also has a property called uwc-homepage which can be changed and is reflected in the 'Home' link on Branding page.

Localizing Mail

Communications Express allows you to localize any feature of Mail. Different pages can be created for different languages. When you create language-specific static pages, you need to group them in subdirectories under the main document directory. The code automatically detects the client’s language preference and fetches the pages from the appropriate subdirectory.

When you change common sections for static pages, you must make the changes on multiple occasions if modifications are desired across languages (for example, if changes are required to modify JavaScript behavior). Conversely, you can also make language-specific modifications selectively throughout the application.

Specific Locales

Code Example 10-1 lists the specific locales and their abbreviations that are supported by Communications Express services. The default language is English.

Table 10-1 Communications Express Specific Locales
Locale	Abbreviation
English	en
Japanese	ja
Spanish	es
French	fr
German	de
Russian	ru
Arabic	ar

Code Example 10-1 shows the changes to be made to the ru/i18n.js file for modifying the charset in the i18n.resource file.

Code Example 10-1 Modifying the charset in the i18n Resource File.

// I18N Resource file
var i18n = new Array()
var fldr = new Array()
// DO NOT TRANSLATE AS STRINGS-JUST VALUES
i18n['client charset'] = 'iso-8859-5'
i18n['http charset'] = 'iso-8859-5'
i18n['fontface'] = 'PrimaSans BT,Verdana,sans-serif
i18n['fontface1'] = i18n['fontface']
i18n['fontface2'] = 'Times New Roman,Times,serif'
i18n['fontface3'] = 'Courier New,Courier,mono'
i18n['nbsp'] = ' '

Communications Express allows you to customize text that is displayed on web pages. This text is both customizable and localizable. The system also allows you to configure text on a per domain basis

To Include Additional Dictionary for Spell Check

Get the dictionary file and the affix file for the language you want to add to your dictionary.

The dictionary file contains language-specific vocabulary and the affix file contains grammar rules for the specific language. For information on dictionary and affix files refer to the site: http://fmg-www.cs.ucla.edu/fmg-members/geoff/ispell-dictionaries.html

Use the buildhash utility to create a platform-specific and language-specific hash file from the dictionary and affix files. This hash file is used by the Communications Express spell checker.

To run the buildhash utility, download the ispell source files available at the site: http//www.gnu.org/software/ispell/ispell.html or, use the buildhash utility in the msg_svr_base/dict/bin directory. The syntax for the buildhash utility is:

buildhash dictionary_file affix_file language_name.hash

The language_name in the language_name.hash file is the two-letter language code used by Communications Express (such as: en for English, fr for French).

To determine your language’s two-letter code, enter the command:

msg_svr_base/msg-instance/configutil | grep local.supportedlanguages



Note	The double-byte character set is not supported by Communications Express spell checker.

Copy the newly created language_name.hash file in the msg_svr_base/dict directory and restart the mshttpd service. When the mshttpd service is restarted, the Communications Express spell checker is enabled.

The following example shows how to create a German hash file (ge.hash) by using the buildhash utility.

Creating a German hash file by using the buildhash utility.

# cd /usr/Sun/server5/dict/bin

# ./buildhash german.dico german.aff ge.hash

# cp ge.hash ..

# /usr/Sun/server5/msg-budgie/start-msg http

, where the file i18n.js controls the text. The i18n.js file also can be localized to fit the language of many regions in the world

Localizing Address Book

To localize address book, the xml file that needs to be modified is the dictionary- <lang>.xml file that is located under <uwcinstalldir> /WEB-INF/ui/html/abs directory.

Customizing Address Book for a Specific Locale

You can customize the Address Book UI either for a specific locale and not under a specific domain and also for a locale under a specific domain.

Customizing the Address Book UI for a locale and not under a specific domain

Create a directory with the locale name(e.g., ja under <uwcinstall>/WEB-INF/ui/html/abs

Copy all files from <uwcinstall>/WEB-INF/ui/html/abs to ..../abs/<locale>

Make the required changes in XSL files as explained in .

Customizing the Address Book for a locale under a specific domain

Create a directory with <domain>/<locale> (e.g., siroe.com/ja) under <uwcinstall>/WEB-INF/ui/html

Copy all files from <uwcinstall>/WEB-INF/ui/html/abs to ..../abs/<locale>

Make the required changes in XSL files as explained in the previous sections.

Previous Contents Index Next
Sun Java System Communications Express 6 2004Q2 Customization Guide