How the Gateway Selects a Character Set
32 Netscape Directory Server Gateway Customization Guide
The NT Synchronization Server, installed with the Directory Server, converts
UTF-8 to and from NT’s Unicode representation (UCS-2).
Note Netscape Communicator 4.x supports UTF-8. Netscape Navigator 3.x does not.
How the Gateway Selects a Character Set
The gateway can output web pages in many character sets. The gateway selects
a character set for each HTTP client based on a combination of input from the
client and from the gateway’s configuration files. Releases 3.x and 4.0 of the
gateway select a character set for transmission according to this priority:
• character set defined in the client’s HTTP Accept-charset header (in release
4.0, this can be overridden for a particular browser using the
ignoreAcceptCharsetFrom parameter).
• character set defined in the client’s HTTP Accept-language header (for
instance, for Japanese, the character set would be defined as ../dsgw/ja/
dsgwcharset.conf)
• character set defined in the gateway’s .conf file by the charset parameter.
How the Gateway Selects from Multiple
Requested Character Sets
When a client includes more than one character set in a request header, and the
gateway supports more than one of these, it selects a character set according to
this priority:
•UTF-8
• of the possible character sets, the character set with the highest Q value (for
example, “de;q=1, en;q=0.5, fr;q=0.7” would give German the highest Q
value)
• the character set that appears first in the request header.
• Latin-1 (ISO-8859-1)
