xBase and Clipper language compatible compiler
PrevNext

Chapter 9. CLIP localisation

9.1. CLIP runtime localisation

9.1.1. The LANG environment variable, directory $CLIPROOT/lang

The CLIP runtime system on program start check existance of some files, and treat it content as environment variables name/value pairs. (See CLIP environment description)

The first useful file is $CLIPROOT/lang/$LANG, where value of CLIPROOT will be taken from environment, or if there is nothing, from builtin (compiled-in) value, and LANG is a value of environment (also known as locale). If LANG is empty, CLIP check also CHARSET variable.

Example 9-1. Sample $CLIPROOT/lang/ru_RU.KOI8-R file

#CLIP_KEYMAP is used in raw keyborard mode
CLIP_KEYMAP=ru-koi8-r

The next file is $CLIPROOT/term/$TERM, where TERM is variable, which identified type of used terminal.

Example 9-2. Sample $CLIPROOT/term/linux-console file

# switch on linux console raw keyboard
CLIP_SCANMODE=IOCTL

9.1.2. Keymaps and keymap table generation.

Keymaps are used in raw keyboard mode, it is possible (for now) on Linux console, and on some kind of terminals, which can be switched into scancode mode by escape sequence.

CLIP use the same keymaps as Linux kernel, and scancode processing is borrowed from the kernel sources. That means, you can easy add new keymaps and to modify it as required.

Adding new keymap:

9.1.3. Charsets, uni-files, utilites for generation

Charsets are used for recoding terminal input and output, for dealing with terminal pseudographics, to determine the sort order, and for recoding file and database in/out througput.

As with keymaps, CLIP use own format for storing charsets, but have utilite for generation from standard charset-to-unicode mapping.

Adding new charset:

PrevHomeNext
Localization Message translation