AUTO_LEXER Language Support
At index time, AUTO_LEXER automatically detects the language of the document, and tokenizes and stems the document appropriately. To specify an AUTO_LEXER dictionary, use the name of the dictionary you created instead of the filename for the dictionary.
At query time, the language of the query is inherited from the query template. If the query template is not used, or if no language is specified in the query template, then the language of the query is inherited from the session language. Table 2-15 lists the supported languages.
Note: Note that dictionary data will not be processed until index/policy creation time or ALTER INDEX time. Errors in dictionary data format will be caught at index/policy creation time or ALTER INDEX time and reported as: DRG-13710: Syntax Error in Dictionary.
Table 15 Languages Supported for AUTO_LEXER
| Language | Language |
|---|---|
| ARABIC | NYNORSK |
| BOKMAL | PERSIAN |
| CROATIAN | SERBIAN |
| DANISH | SLOVAK |
| FINNISH | SLOVENIAN |
| HEBREW | THAI |
| CATALAN | KOREAN |
| CZECH | POLISH |
| DUTCH | PORTUGUESE |
| ENGLISH | ROMANIAN |
| FRENCH | RUSSIAN |
| GERMAN | SIMPLIFIED CHINESE (See Note) |
| GREEK | SPANISH |
| HUNGARIAN | SWEDISH |
| ITALIAN | TRADITIONAL CHINESE (See Note) |
| JAPANESE | TURKISH |
Note: Due to the limitation of 30 characters for the string, Traditional Chinese must be specified as trad_chinese. Simplified Chinese must be specified as simp_chinese.