17 Globalization Notes

This module contains the following types of information on Oracle Beehive globalization:

• General Globalization Notes

• Known Limitations and Workarounds with Globalization

• Known Issues with Oracle Beehive Globalization

General Globalization Notes

This section contains general information about Oracle Beehive globalization, and includes the following topic:

• Notifications

Notifications

Notifications generated in one non-English character set and displayed in a different non-English locale may have corrupted characters. For example, a meeting notification with a location in Japanese, shown to a client running in a German locale, may not properly display the Japanese characters.

Known Limitations and Workarounds with Globalization

This section contains information on known globalization limitations and workarounds, and includes the following topics:

• Korean, Simplified Chinese, and Traditional Chinese Not Supported in Cisco IP Communicator

• Using the Save As Function in Microsoft Internet Explorer Modifies Non-ASCII File Names

• Verisign Does Not Support UCS-2 Encoding in SMS Messages

• Oracle Beehive Supports ASCII Characters in Users' Native Languages Only

Korean, Simplified Chinese, and Traditional Chinese Not Supported in Cisco IP Communicator

Bug 6908257. Cisco IP Communicator (soft phone) does not support Korean, Simplified Chinese, and Traditional Chinese.

Using the Save As Function in Microsoft Internet Explorer Modifies Non-ASCII File Names

Note:

This limitation only applies for users who access Oracle Beehive workspaces with Microsoft Internet Explorer Version 6 in Windows XP with the Simplified Chinese language pack.

Bug 6939991. Using the Save As function on a file that has non-ASCII characters in its file name will modify the file name by removing some characters. This limitation affects only the file names themselves. It does not affect file type extensions or any non-ASCII text contained in files.

Verisign Does Not Support UCS-2 Encoding in SMS Messages

Bug 7164221. Verisign does not support UCS-2 encoding, which is required to encode non-English ASCII characters in SMS messages. As a result, any non-English ASCII characters in SMS messages will appear corrupted and unreadable to users.

Oracle Beehive Supports ASCII Characters in Users' Native Languages Only

Bugs 6120654, 6359278, and 7706764. Oracle Beehive supports ASCII characters in users' native languages only. In other words, Oracle Beehive will only display the ASCII characters supported by each locale. In cases where ASCII or non-ASCII characters from one locale must be displayed in the another locale, Oracle Beehive may replace unsupported characters with questions marks (?) or other characters.

This limitation can manifest itself in the following ways:

• Bugs 6120654 and 6359278. If your deployment's user directory contains ASCII or non-ASCII characters from multiple locales, users in one locale will not see the correct characters from other locales.

• Bug 7706764. In FileZilla 3.2.0, Oracle Beehive may replace unsupported characters with questions marks (?) or other characters in folder and file names, including when users double-click file names to create new branches in their directory trees.

Known Issues with Oracle Beehive Globalization

This section contains information on known issues with Oracle Beehive globalization, and includes the following topic:

• Task Notifications Sent to Users in French (Canadian) Locale May Contain Additional Characters

Task Notifications Sent to Users in French (Canadian) Locale May Contain Additional Characters

Note:

This issue is resolved in Oracle Beehive Release 1 (1.5.1.2) and later.

Bug 7716276. Notifications for new tasks that are sent to users configured for the French (Canadian) locale may contain additional characters. These characters, which typically appear at the top of the notification, do not impact the integrity of the notification and, therefore, can be ignored.