CLIP applications are able to work with all kind of terminals and emulators. Terminal abilities descriptions are available at terminfo database or (if environment variable TERMCAP is set) at the file TERMCAP is indicating on. On addition to this descriptions there are some extended possibilities to indicate for CLIP application some special capabilities of terminal. These descriptions are in directory $CLIPROOT/term and looking as
file term/linux-stelnet # to work with description of linux terminal in terminfo +TERM=linux # whether yielding scan-codes instead of ansi-codes terminal ability; # options are: terminal, ioctl, no CLIP_SCANMODE=terminal # ESC-sequence to switch scan-codes transfer mode on CLIP_SCANSTART=\033[S # ESC-sequence to switch scan-codes transfer mode off CLIP_SCANSTOP=\033[R # keyboard layout for keyboard driver of CLIP application CLIP_KEYMAP=rustelnet # charset used by CLIP VM at run time // unicode - file CLIP_HOSTCS=koi8-r # charset used by client for display // unicode - file CLIP_CLIENTCS=cp866 # single pseudo-graphics symbols CLIP_LINECHARS=\200\201\204\211\205\206\212\207\202\210\203 # double pseudo-graphics symbols CLIP_DLINECHARS=\240\241\253\273\256\261\276\265\245\270\250 # color translation table CLIP_COLORMAP=0123456789ABCDEF
All "advanced" terminal names have to be registered in your terminfo/termcap database.
Linux standard unicode-tables located in /usr/share/consoletrans directory are used for translation of terminal output.
Necessary unicode-tables have to be unpacked and put into $CLIPROOT/charsets directory. CLIP distribution contains some unicode-tables also.