Installation guide

Table Of Contents
Special Characters
Chapter 3 Gateway Localization 45
HTTP Clients that Do Not Request UTF-8
For browsers that do not request UTF-8 by default, the gateway selects a character set from
the
Accept-Charset request header or from the Accept-Language request header,
depending on the HTTP client.
Some HTTP clients don't request any character set information. For these clients, the
gateway's charset parameter definition is the default. When the charset parameter is not
defined in the
dsgw.conf file, the gateway uses Latin-1 (which is the default in HTTP).
In addition to UTF-8 and Latin-1, the gateway can convert to and from several national
character sets, depending on the client's needs and configuration, including the following:
Shift_JIS
•Big5
•EUC-KR
Special Characters
The following sections describe how special characters are interpreted by the gateway:
Non-Breaking Space
Query Strings
Non-Breaking Space
If the client's character set lacks a character for non-breaking space, but has ideographic
space, non-breaking spaces are converted to ideographic spaces before charset conversion.
See the
changeHTML directive (page 93) in the gateway configuration file dsgw.conf.
Query Strings
When the gateway needs to embed a UTF-8 string in a URL, it encodes it in a query string
(the query string is the part of the URL that follows the question mark).