Appendix D
Internationalized iPlanet Web Server
The internationalized version of the iPlanet Web Server contains special features tailored for the non-U.S. environment. These features include a choice of user-interface language (Japanese, French, or German) and a choice of search engines that allow you to use text search on a variety of languages.
This appendix contains the following sections:
General Information
The following information covers the international considerations for general server capabilities:
Installing the Server
When you install the server, you choose what user-interface language to use, as well as what search engines to install.
For information on installing the international version of the server, see the iPlanet Web Server, Enterprise Edition 6.0 Release Notes. You can access the Release Notes online via the link provided in the README file.
Entering UTF-8 Data
If you want to enter UTF-8 data on the Server Manager or the Administration Server pages, you need to be aware of the following issues:
File or Directory Names
If a file or directory name is to appear in a URL, it cannot contain 8-bit or multi-byte characters.
LDAP Users and Groups
For email addresses, use only those characters permitted in RFC 1700 (ftp://ds.internic.net/rfc/rfc1700.txt). User ID and password information must be stored in ASCII.
If you must use 8-bit or multi-byte characters in your directory database, you should store them in UTF-8 for future compatibility with an LDAPv3 compliant directory server. To make sure you enter characters in the correct format, use a UTF-8 form-capable client (such as Netscape Communicator) to input 8-bit or double-byte data.
If you let users access their own user and group information, they will need to use a UTF-8 form-capable client.
Using the Accept Language Header
When clients contact a server using HTTP 1.1, they can send header information that describes the various languages they accept. You can configure your server to parse this language information.
For example, suppose this feature is set to on, and a client configured to send the accept language header sends it with the value en,fr. Now suppose that the client requests the following URL:
-
http://www.someplace.com/somepage.html
The server first looks for:
-
http://www.someplace.com/en/somepage.html
If it does not find that, it looks for:
-
http://www.someplace.com/fr/somepage.html
If that is not available either, and a ClientLanguage (call it xx) is defined in the magnus.conf file, the server tries:
-
http://www.someplace.com/xx/somepage.html
If none of these exist, the server tries:
-
http://www.someplace.com/somepage.html
Language Settings in Configuration Files
The following directives in the magnus.conf file affect languages:
Table D-1 International Settings in magnus.conf
|
Directive
|
Values
|
Description
|
|
ClientLanguage
|
en, fr, de, ja
|
Specifies the language in which client messages, such as "Not Found" or "Access denied" are to be expressed. This value is used to identify a directory containing ns-https.db.
|
|
DefaultLanguage
|
en, fr, de, ja
|
Specifies the language used if a resource cannot be found for the client language or the administration language.
|
The following directive in the server.xml file affect languages:
Figure D-1 International Settings in server.xml
|
AcceptLanguage
|
on, off
|
Enables or disables the Accept language header parsing.
|
Character Sets
iPlanet Web Server supports the following character sets:
Japanese-sjis (932) and eucjp
Simplified Chinese-Gb (936)
Traditional Chinese-big5 (950)
Korean-ksc (949)
Search Information
Search capabilities are supported for the following languages:
English
German
French
Italian
Spanish
Swedish
Dutch
Japanese
Korean
Simplified Chinese
Traditional Chinese
You choose which search engines to install when you install the international version of the server.
This section includes the following topics:
International Search
If your server contains documents in various character set encodings, the search collections and/or auto catalog for the documents will inherit the same encodings as the originals. To view documents in different character set encodings, users must change the character set encoding for their browsers. In addition, since the text search and auto catalog features work with one character set encoding at a time, you might receive inaccurate results when using those features. For best results, use one specific character set for all documents.
Searching in Japanese, and Korean
The following information is specific to searching in Japanese and Korean.
Query Operators
This release supports the following query operators for Japanese and Korean languages:
Table D-2 Query operators for Japanese
|
Operator
|
J/C/K Character
|
|
AND
|
Yes
|
|
CONTAINS
|
No
|
|
ENDS
|
Yes
|
|
MATCHES
|
Yes
|
|
NEAR
|
Yes
|
|
NEAR/N
|
Yes
|
|
NOT
|
Yes
|
|
OR
|
Yes
|
|
PHRASE
|
Yes
|
|
STARTS
|
Yes
|
|
STEM
|
English only
|
|
SUBSTRING
|
Yes
|
|
WILDCARD *
|
Yes
|
|
WILDCARD ?
|
Yes
|
|
WORD
|
Yes
|
Document Formats
This release supports the following document formats for the Japanese and Korean languages:
Searching in Japanese
The following sections give additional information about searching in the Japanese character set.
Document Codes
This release supports the following document codes for the Japanese language:
Search Words
This release supports the following search words:
kanji
hiragana
katakana (full-width and half-width)
ASCII (full-width and half-width)
The search engine translates half-width katakana to full-width katakana, and translates full-width ASCII to half-width ASCII. Users can use full-width and half-width as the same characters.
This release also supports phrase and sentence search.
Using International Character Sets in Servlets
iPlanet Web Server allows you to specify the character encoding with the parameter-encoding element, <parameter-encoding enc="<value>", in web-apps.xml file. The value can be set as one of the following:
Parameter Encoding Values
For more information on parameter-encoding, see the Programmer's Guide to Servlets.
Auto
Auto requires the servlet container to look for some hints for the character encoding to be used. The server will always try to resolve the charset from the Content-Type header of the request first. Since that may not always be available, another hint can be specified as:
A request attribute using the name: com.iplanet.server.http.servlet.parameterEncoding. The value is of type String. The request attribute must be set before any calls to getParameter() or getParameterValues(). Example:
-
request.setAttribute("com.iplanet.server.http.servlet.parameterEncoding", "Shif t_JIS"); request.getParameter("test");
-
This option is used if the servlet that is reading the data knows beforehand what the charset of the posted data is.
A j_encoding parameter in the form data. The form that is being submitted can have a hidden element:
-
<input type=hidden name="j_encoding" value="Shift_JIS" >
-
This option is typically used if the servlet that is reading the data does not necessarily know what the charset of the posted data is. The hint parameter name, which by default is j_encoding can be changed using parameter-encoding element in web-apps.xml.
None
Use this option if you wish the platform default encoding to be used for the servlet parameter data.
utf8
If none of the above options are specified, the servlet container interprets this string itself as the encoding, so this can be any valid encoding string like Shift_JIS, or UTF8. For example, you would specify this as UTF-8 if you know that the form POST data is always in UTF-8.
Posting to JSPs
If you are posting to a JSP instead of to a servlet, the same holds true. For example, a JSP configured to `auto' to read parameters which are in Japanese Shift_JIS encoding:
<%@ page contentType="text/html;charset=Shift_JIS" %>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=Shift_JIS">
<title>JSP Test Case</title>
</head>
<body>
<%
request.setAttribute("com.iplanet.server.http.servlet.parameterEnco
ding", "Shift_JIS");
%>
<h1>The Entered Name is : <%= request.getParameter("test") %>
</h1>
</body>
</html>