Compiled terminfo descriptions are placed under the direc-
tory /usr/share/terminfo. Two configurations are sup-
ported (when building the ncurses libraries):
@@ -89,16 +87,17 @@
directory tree for entries that correspond to an
existing directory, and hashed database otherwise.
- STORAGEFORMAT
+
+
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.
- The compiled file is created with the tic program, and
- read by the routine setupterm. The file is divided into
- six parts: the header, terminal names, boolean flags, num-
- bers, strings, and string table.
+ The compiled file is created with the tic program, and
+ read by the routine setupterm(3x). The file is divided
+ into six parts: the header, terminal names, boolean flags,
+ numbers, strings, and string table.
The header section begins the file. This section contains
six short integers in the format described below. These
@@ -113,7 +112,7 @@
(4) the number of short integers in the numbers sec-
tion;
- (5) the number of offsets (short integers) in the
+ (5) the number of offsets (short integers) in the
strings section;
(6) the size, in bytes, of the string table.
@@ -133,7 +132,7 @@
The terminal names section comes next. It contains the
first line of the terminfo description, listing the vari-
- ous names for the terminal, separated by the `|' charac-
+ ous names for the terminal, separated by the "|" charac-
ter. The section is terminated with an ASCII NUL charac-
ter.
@@ -167,7 +166,8 @@
the values of string capabilities referenced in the string
section. Each string is null terminated.
- EXTENDEDSTORAGEFORMAT
+
+
The previous section describes the conventional terminfo
binary format. With some minor variations of the offsets
(see PORTABILITY), the same binary format is used in all
@@ -197,7 +197,7 @@
bytes.
Using the counts and sizes, ncurses allocates arrays and
- reads data for the extended capabilties in the same order
+ reads data for the extended capabilities in the same order
as the header information.
The extended string table contains values for string capa-
@@ -206,15 +206,14 @@
e.g., booleans, then numbers and finally strings.
-
-
PORTABILITY
- Note that it is possible for setupterm to expect a differ-
+
+ Note that it is possible for setupterm to expect a differ-
ent set of capabilities than are actually present in the
file. Either the database may have been updated since
- setupterm has been recompiled (resulting in extra unrecog-
+ setupterm has been recompiled (resulting in extra unrecog-
nized entries in the file) or the program may have been
recompiled more recently than the database was updated
- (resulting in missing entries). The routine setupterm
+ (resulting in missing entries). The routine setupterm
must be prepared for both possibilities - this is why the
numbers and sizes are included. Also, new capabilities
must always be added at the end of the lists of boolean,
@@ -232,8 +231,7 @@
sion of terminfo source compatibility issues.
-
As an example, here is a hex dump of the description for
the Lear-Siegler ADM-3, a popular though rather stupid
early terminal:
@@ -270,25 +268,21 @@
-