WebSphere Message Broker converts any message that is loaded from the code pages that are listed below into the local code page of the running processes (brokers) before output to the syslog.
You must provide symbolic links to your primary message catalogs for all locales that you intend to support. WebSphere Message Broker uses the LC_MESSAGES variable when opening message catalogs.
When building a message file for Windows that
contains multiple locales, ensure that the computer's locale is set to a western
European locale (for example, English (United Kingdom)) before building the
message catalogs. Use the chcp (Change Code Page) command
to ensure that the code page is 850.
Write or convert all your message files (those with file type .mc) to the following code pages; each message file should be compiled separately by the message compiler with the additional flag that is specified in the following table.
DBCS message files do not need to be in Unicode (no -U flag). Use the RC command to 'resource compile' all the files and then use the link command to build a single message dll.
Locale | Code page | Additional Flags |
---|---|---|
English (United States) | 437 | -U |
German (Standard) | 850 | -U |
Spanish (Modern Sort) | 850 | -U |
French (Standard) | 850 | -U |
Italian (Standard) | 850 | -U |
Portuguese (Brazilian) | 850 | -U |
Japan | 932 | |
Simplified Chinese (China) | 1381 | |
Traditional Chinese (Taiwan) | 950 | |
Korean | 949 |
When building message catalogs for Linux and UNIX, ensure that the catalogs are built in the following code pages:
Locale | Code page |
---|---|
English | 437 |
German | 850 |
Spanish | 850 |
French | 850 |
Italian | 850 |
Portuguese (Brazilian) | 850 |
Japan | 932 |
Simplified Chinese (China) | 1381 |
Traditional Chinese (Taiwan) | 950 |
Korean | 949 |