NAME

SYNOPSIS

DESCRIPTION

idnkit library tries to load the user's configuration file ~/.idnrc first, and then tries the system configutation file /usr/local/etc/idn.conf. Note that idnkit library loads either, not both.

To use internationalized domain names in DNS or other protocols, they must be converted to an appropriate format before further processing. In idnkit, this conversion process is comprised of the following tasks.

1.

Convert the given domain name in application's local codeset to Unicode, and vice versa.

2.

Map certain characters in the name to period character so that they are treated as the domain name delimiter (delimiter mapping).

3.

Map certain characters in the name to other characters or chracter sequences, according to a mapping rule determined by its top level domain (TLD).

4.

Perform NAMEPREP, which is a starndard name preparation process for internationalized domain names. This process is composed of the tree steps called mapping, normalization, prohibited character checking and bidirectional string checking.

5.

Convert the nameprepped name to IDN encoding, which is the standard encoding for internationalized domain names (also known as ASCII-compatible encoding, ACE), and vice versa.

The configuration file specifies the parameters for these tasks, such as:

SYNTAX

keyword value..

IDN-ENCODING ENTRY

The syntax of this entry is:

idn-encoding encoding

encoding is the encoding name to be used, and any of the following names can be specified.

The standard encoding was determined as Punycode.

NAMEPREP ENTRY

The syntax of this entry is:

nameprep version

version is the version name of NAMEPREP specification, and currently the following versions can be specified.

The NAMEPREP process consists of the following 4 subprocesses.

1.

mapping, which maps certain characters in a name to other characters, possibly none.

2.

normalization, which replaces character variants in a name to a unique one.

3.

prohibited character checking, which detects invalid characters in a name.

4.

unassigned codepoint checking, which also invalid codepoints in a name.

5.

bidirectional string checking, which detecs invalid string.

LOCAL-MAP ENTRY

The syntax of this entry is:

local-map tld scheme [scheme..]

tld specifies the TLD to which the mapping rule is to be applied, and scheme specifies the mapping scheme, and currently available schemes are:

There are two special tlds for specifying the mapping rule for local domain names (domain names without any dots in them), and the default mapping rule. If tld is ``-'', it matches domain names which do not contain any dots. If tld is ``.'', it matches any domain names which don't match to any other mapping rules specified by ``local-map'' entries.

MAPFILE FORMAT

A mapfile is a simple text file, and each line specifies a single mapping. Each line is of the form:

src-codepoint; mapped-codepoint-seq;

src-codepoint indicates source character of the mapping, and must be a Unicode codepoint value in hexadecimal string. mapped-codepoint-seq is a sequence of characters which is the outcome of the mapping, and must be a (possibly empty) list of Unicode codepoint values in hexadecimal string, separated by spaces.

Lines which begin with ``#'' are treated as comments and ignored.

A sample mapfile is shown below.

# map "A" to "a"
0041; 0061;
# map "#" to nothing
0023; ;
# map "@" to "at"
0040; 0061 0074;

LOCAL CODESET

Although idnkit tries hard to find out the local codeset, sometimes it fails. For example, there are applications which use non-ASCII codeset but work in C locale. In this case, you can specify the application's local codeset by an environment variable ``IDN_LOCAL_CODESET''. Just set the codeset name (or its alias name) to the variable, and idnkit will use the codeset as the local one, regardless of the locale setting.

ENCODING-ALIAS-FILE

The alias file is a simple text file, consisting of lines of the form:

alias-name name

alias-name is the alias name to be defined, and name is the real name or another alias name.

SAMPLE CONFIGURATION

#
# a sample configuration.
#
# Use Punycode as the IDN encoding.
idn-encoding Punycode
# Use RFC3491 as NAMEPREP.
nameprep RFC3491
# Perform Japanese-specific mapping for .jp domain.
# assuming /usr/local/lib/idnkit/jp-map contains the mapping.
local-map .jp filemap:/usr/local/lib/idnkit/jp-map

FILES

SEE ALSO