UTF-8
[Previous] [Next]
[First] [Last]
UTF-8
Introduction
Netscape Calendar Server 3.5 uses UTF-8, an 8 bit encoding of 16 bit UNICODE,
to achieve an international character representation on the server.
Any data entered in the following fields will be converted to UTF-8
format :
Records
|
Fields
|
UNIAPI_ITEM (all user & resource information) |
ALL |
UNIAPI_GROUP |
Name, AddInfo |
Configuration
The following parameter is set in the unison.ini file. To verify
that the value is set to TRUE (a requirement for Netscape Calendar Server
3.5 or higher), select Server Preferences | Manage Calendar Server
from the Calendar Server Manager.
Section
[ENG]
Parameter
utf8_autoconvert
-
Description
-
This parameter enables or disables the conversion of input data to UTF-8.
For any implementation of Netscape Calendar Server 3.5 or higher, this
parameter must be set to TRUE.
-
Accepted values
-
TRUE (UTF-8 conversion is enabled)
-
FALSE (UTF-8 conversion is disabled)
-
Default value
The default value is TRUE
Character set identification
process
All conversions to UTF8 are done in the server (uniengd).
In order to successfully complete the conversion, the server must know
which character set will be received from the client. Future releases
of the Netscape Calendar Client (5.x and above), will supply this information.
For earlier releases (Netscape Calendar Client 4.x and below) the identification
of the appropriate character set is achieved through the following process:
-
The third parameter (other) of ClientIdentifyToServer()
is read for Netscape Calendar Client 5.x and above. Earlier versions
of the client cannot identify their character set to the server at this
stage. The format for returned values is "charset=macroman8" or
"charset=mscp1251", etc.
-
If the other parameter of ClientIdentifyToServer()is
not specified (such as for older clients), the unison.ini file
will be read to find a match for a sub-string of the name parameter of
ClientIdentifyToServer(). The appropriate node section is
searched first, followed by the [LOCALE] section. Information found in
the node section takes precedence over that found in the [LOCALE] section.
In addition, a more explicitly defined parameter takes precedence over
a more general definition; for example charsetwindows32 takes
precedence over charsetwindows.
-
If an appropriate parameter is not configured in the unison.ini
file, the following defaults are assumed:
-
If no match is found in any of the preceding steps, the following unison.ini
file parameter is used with ISO88591 as the default.
-
In the rare event that it was not possible to identify a client character
set in any of the above steps, UTF-8 conversion is disabled
and the server will process the data in RAW mode.
Once a character set is selected by the server, the corresponding character
map file is read in from the users/unison/etc/charset directory.
[Previous] [Next]
[First] [Last]