Product Documentation

FairCom ISAM for C

Previous Topic

Next Topic

Server Configuration Keywords for Unicode Segment Default

The FairCom Server configuration file (or settings file or command line) can specify a server default for each type of extended segment definition supported. Each such default definition starts with a XTDKSEG_SEG_TYPE entry. For an ICU Unicode default, the entries begin with

XTDKSEG_SEG_TYPE UNICODE_ICU

This initial entry is then followed by the specifics of the default such as locale and other collation options. For example, the following configuration entries would define a default for the server with the same characteristics as the application default used in the above API example.

XTDKSEG_SEG_TYPE UNICODE_ICU

ICU_LOCALE "ar"

XTDKSEG_SRC_SIZE 12

XTDKSEG_SRC_TYPE UTF8

ICU_OPTION STRENGTH_TERTIARY

ICU_OPTION NORM_DEFAULT

The complete list of keywords and arguments is shown in the following table.

Configuration Keyword

Arguments

XTDKSEG_SEG_TYPE

UNICODE_ICU

XTDKSEG_SRC_TYPE

PROVIDED

UTF-8

UTF-16

XTDKSEG_SRC_SIZE

PROVIDED

COMPUTED

<numeric value>

XTDKSEG_FAILED_DEFAULT_OK

YES [server can still begin if server default encounters an error]

NO [server cannot continue on error, which is the default behavior]

ICU_LOCALE

<locale string in ICU form: xx_YY_Variant> *

ICU_OPTION

STRENGTH_PRIMARY

STRENGTH_SECONDARY

STRENGTH_TERTIARY

STRENGTH_QUATERNARY

STRENGTH_IDENTICAL

STRENGTH_DEFAULT

NORM_NONE

NORM_CAN_DECMP

NORM_CMP_DECMP

NORM_CAN_DECMP_CMP

NORM_CMP_DECMP_CAN

NORM_DEFAULT

LOCALE_SYSDEFAULT_NOTOK

LOCALE_FALLBACK_NOTOK

ATTR_FRENCH_ON

ATTR_FRENCH_OFF

ATTR_CASE_ON

ATTR_CASE_OFF

ATTR_DECOMP_ON

ATTR_DECOMP_OFF

ATTR_SHIFTED

ATTR_NONIGNR

ATTR_LOWER

ATTR_UPPER

ATTR_HANGUL

* Where “xx” is the language as specified by ISO-639 (e.g., “fr” for French); ‘Y’ is a country as specified by ISO-3166 (e.g., “fr_CA” for French language in Canada); and the “Variant” portion represents system dependent options.

For all but ICU_OPTION, only one of the listed arguments can be specified for each keyword. For instance, it does not make sense to have both of these entries in the configuration file for one extended key segment default definition:

XTDKSEG_SRC_TYPE UTF16

XTDKSEG_SRC_TYPE UTF8

There may be many ICU_OPTION entries in a configuration file. Some combinations of entries do not make sense, and the behavior is not guaranteed if they are combined. For instance, using both of these entries is inappropriate:

ICU_OPTION ATTR_LOWER

ICU_OPTION ATTR_UPPER

TOCIndex