NAME<\/a> term \u2212 format of compiled term file.<\/p>\n term<\/b><\/p>\n STORAGE LOCATION<\/b> A two-level scheme is used to avoid a linear search of a huge UNIX<\/small> system directory: \/usr\/share\/terminfo\/c\/name<\/b> where name<\/i> is the name of the terminal, and c<\/i> is the first character of name<\/i>. Thus, act4<\/i> can be found in the file \/usr\/share\/terminfo\/a\/act4<\/b>. Synonyms for the same terminal are implemented by multiple links to the same compiled file.<\/p>\n hashed database<\/b><\/p>\n Using Berkeley database, two types of records are stored: the terminfo data in the same format as stored in a directory tree with the terminfo\u2019s primary name as a key, and records containing only aliases pointing to the primary name.<\/p>\n If built to write hashed databases, ncurses<\/b> can still read terminfo databases organized as a directory tree, but cannot write entries into the directory tree. It can write (or rewrite) entries in the hashed database.<\/p>\n ncurses<\/b> distinguishes the two cases in the TERMINFO and TERMINFO_DIRS environment variable by assuming a directory tree for entries that correspond to an existing directory, and hashed database otherwise.<\/p>\n LEGACY STORAGE FORMAT<\/b> The compiled file is created with the tic<\/b> program, and read by the routine setupterm<\/b>(3X). The file is divided into six parts:<\/p>\n a) header<\/i>, The header<\/i> section begins the file. This section contains six short integers in the format described below. These integers are<\/p>\n (1) the magic number<\/i> (octal 0432); The capabilities in the boolean flags<\/i>, numbers<\/i>, and strings<\/i> sections are in the same order as the file Short integers are signed, in the range \u221232768 to 32767. They are stored as two 8-bit bytes. The first byte contains the least significant 8 bits of the value, and the second byte contains the most significant 8 bits. (Thus, the value represented is 256*second+first.) This format corresponds to the hardware of the VAX<\/small> and PDP<\/small> -11 (that is, little-endian machines). Machines where this does not correspond to the hardware must read the integers as two bytes and compute the little-endian value.<\/p>\n Numbers in a terminal description, whether they are entries in the numbers<\/i> or strings<\/i> table, are positive integers. Boolean flags are treated as positive one-byte integers. In each case, those positive integers represent a terminal capability. The terminal compiler tic uses negative integers to handle the cases where a capability is not available:<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
PORTABILITY<\/a>
EXAMPLE<\/a>
LIMITS<\/a>
FILES<\/a>
SEE ALSO<\/a>
AUTHORS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
Compiled terminfo descriptions are placed under the directory \/usr\/share\/terminfo<\/b>. Two configurations are supported (when building the ncurses<\/b> libraries):
directory tree<\/b><\/p>\n
The format has been chosen so that it will be the same on all hardware. An 8 or more bit byte is assumed, but no assumptions about byte ordering or sign extension are made.<\/p>\n
b) terminal names<\/i>,
c) boolean flags<\/i>,
d) numbers<\/i>,
e) strings<\/i>, and
f) string table<\/i>.<\/p>\n
(2) the size, in bytes, of the terminal names<\/i> section;
(3) the number of bytes in the boolean flags<\/i> section;
(4) the number of short integers in the numbers<\/i> section;
(5) the number of offsets (short integers) in the strings<\/i> section;
(6) the size, in bytes, of the string table<\/i>.<\/p>\n