| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
This module contains the following types of information on Oracle Beehive globalization:
This section contains general information about Oracle Beehive globalization, and includes the following topic:
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.
This section contains information on known globalization limitations and workarounds, and includes the following topics:
Error When Logging In to Oracle Beehive Integration for Outlook for the First Time
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
Oracle Beehive Supports ASCII Characters in Users' Native Languages Only
Note:
This issue is resolved in Release 1 (1.3) and later.Bug 6312955. When logging in to Oracle Beehive Integration for Outlook for the first time using a non-English locale, the following error message may appear:
Language id [language_id] is not supported by Oracle Beehive Integration for Outlook. Do you want to use English?
Click Yes to proceed with the login.
Bug 6908257. Cisco IP Communicator (soft phone) does not support Korean, Simplified Chinese, and Traditional Chinese.
Note:
This requirement applies to Release 1 (1.2) only.Microsoft Windows XP Service Pack 2 or later is required on Windows XP computers where users intend to leverage non-English locales with Oracle Beehive Integration for Outlook. Attempting to run Oracle Beehive Integration for Outlook with a non-English locale on a computer with Windows XP Service Pack 1 (or earlier) may result in the computer failing to operate normally.
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.
Note:
This issue is resolved in Release 1 (1.3) and later.Bug 6140900. Users running Oracle Beehive Integration for Outlook with non-English locales on computers with Windows Vista and User Account Control (UAC) enabled may receive an error dialog window upon login. The dialog indicates that the current language is not supported, and it asks users if they want to use English instead. This issue can be resolved if the user logs in to Oracle Beehive Integration for Outlook as an administrator, that is, by selecting the "Run as Administrator" option at login.
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.
Bugs 6120654, 6359278, 6388916, 7324443, and 7325778. 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, 6359278, and 6388916. 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 7324443. If you create an e-mail and attach a file with a name that contains locale-specific characters or special characters (apostrophes, quotation marks, and so forth), Oracle Beehive may not display the correct characters in the file name for users in other locales.
Bug 7325778. When creating a meeting entry in Oracle Beehive Integration for Zimbra, attaching a file with locale-specific characters or special characters (apostrophes, quotation marks, and so forth) in the file name may result in a network error.
