README
file.
ftp://ds.internic.net/rfc/rfc822.txt
). User ID and password information must be stored in ASCII.
If you use a local database, you can enter 8-bit and multi-byte characters, but you should standardize on one character set. If you use more than one character set in the same database, it can cause display and search problems.
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 the Netscape Directory Server version 3.x. 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.
en,fr
. Now suppose that the client requests the following URL:
The server first looks for:http://www.
someplace
.com/
somepage
.html
If it does not find that, it looks for:http://www.
someplace
.com/en/
somepage
.html
If that is not available either, and ahttp://www.
someplace
.com/fr/
somepage
.html
ClientLanguage
(call it xx
) is defined in the magnus.conf
file, the server tries:
If none of these exist, the server tries:http://www.
someplace
.com/xx/
somepage
.html
For information about configuring the server to parse the accept language header, see "Parsing the accept language header" on page 59.http://www.
someplace
.com/
somepage
.html
Language settings in configuration files
The following directives in the magnus.conf
file affect languages:
The following directives in the ns-admin.conf
file affect languages:
Server-side JavaScript information
When you use server-side JavaScript with the international version of the server, you have additional things to consider when compiling applications and using databases. For example, you can specify the language of the JavaScript application one of two ways: using the compiler, or using the HTML <META>
tag.
Specifying the character set for the compiler
For the international version, the server-side JavaScript compiler (jsac
) has a -l
option called charSet
. This option specifies the character set being used in the input HTML files. The value for charSet
is one of the following character set names.
Usage
To use this option, use the following format:
jsac [-cdv] [-l
charSet
] -o binaryFile
[-i] inputFile1
[-i] inputFile2
...
jsac [-cdv] -o
binaryFile
-f includeFile
jsac -h
Options
The following table shows the options for the compiler.
The possible filename extensions are summarized in the following table:
Extension | File type |
---|---|
.html or .htm
| HTML source file (may include JavaScript) |
.js
| JavaScript source file |
.web
| Binary output file |
When you specify the language using the compiler option, you can only specify one language. If you want to specify multiple languages, you can use the <META>
tag in the individual files.
Specifying the character set with the <META> tag
You can also use the <META>
tag to specify the character set information. For example, if you put the following statement into the header (between <HEAD>
and </HEAD>
) in a JavaScript program, the server-side JavaScript compiler (jsac
) considers the file to be written in x-sjis
.
<META HTTP-EQUIV="Content-Type" CONTENT="test/html; CHARSET=x-sjis">
If the character set specified in the <META>
tag is different from the character set specified by the compiler's charSet
option, the character set specified by the compiler option is used.
Using server-side JavaScript with Oracle's Japanese database
To use server-side JavaScript with Oracle's Japanese database, follow these overall steps. Details for each step are in the following sections.
Installing Oracle and setting up your environment
You must first install the Japanese Oracle database. For instructions, see the documentation that came with your database. Next, you must set up your environment variables using the following information. Note that the environment variable syntax assumes C Shell.
Server-side JavaScript library:
setenv LD_LIBRARY_PATH
server_root
/bin/https:$LD_LIBRARY_PATH
setenv ORACLE_HOME
oracle_root
for example, /usr/oracle7
setenv ORACLE_SID
oracle_service_ID
for example, WG73
setenv TNS_ADMIN
path_to_tnsnames.ora
for example
, /.../tnsnames.ora
setenv NLS_LANG
language_charset_info
for example, japanese_japan.JA16EUC
x-euc-jp
)
setenv PATH
server_root
/bin/https:$ORACLE_HOME/bin:$PATH
dbadmin
.
Field | Value |
---|---|
Server Type |
ORACLE
|
Server Identifier |
WG73
|
User ID |
system
|
Password |
manager
|
Database |
|
Unless you see an error indicating otherwise, you are now connected.
Verifying the language setup
Use the videoapp
sample application to verify the language setup.
start.htm
file at the following line:
project.sharedConnections.pool =
new DbPool("ORACLE","WG73", "system", "manager", "", 2, false)
vidoeapp
.
videoapp
home page, and then click Save Changes.
Putting the Oracle client and database server on separate hosts
To put the Oracle client (with server-side JavaScript database service) and the Oracle database server on separate hosts, follow these steps:
SERVER SID
alias to refer to the server in tnsnames.ora
.
the TWO_TASK
environment variable to the SERVER SID
alias defined in the tsnames.ora
file.
setenv TWO_TASK SERVER SID alias
NLS_LANG
environment variable to the correct client language and character set information.
videoapp
, edit the start.htm
file as shown below. (In this example, assume that the SERVER SID
alias is remoteDB
.)
project.sharedConnections.pool = new
DbPool("ORACLE","remoteDB", "system", "manager", "",
2, false)
videoapp
home page, and then click Save Changes.
Search information
Search capabilities are supported for the following languages:
Document formats
This release supports the following document formats for the Japanese, Korean, and Chinese languages:
euc
sjis
jis
(7-bit)