X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fterm.5.html;h=690985ea41288ec9b3e2469c6cd4e76cdd18739d;hp=221db40a87812da81fa7a88b6121e2dc006e0ecf;hb=ce4803687b821efbc5fb2c5a5f06d69cd4dc2656;hpb=027d0c57c4c4d6690e8d8727888d3282dbe9aa86
diff --git a/doc/html/man/term.5.html b/doc/html/man/term.5.html
index 221db40a..690985ea 100644
--- a/doc/html/man/term.5.html
+++ b/doc/html/man/term.5.html
@@ -1,6 +1,6 @@
@@ -45,21 +45,17 @@
-
-
+
term - format of compiled term file.
-
-
+
term
-
-
+
-
-
+
Compiled terminfo descriptions are placed under the direc-
tory /usr/share/terminfo. Two configurations are sup-
ported (when building the ncurses libraries):
@@ -92,17 +88,16 @@
existing directory, and hashed database otherwise.
-
-
+
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.
+ 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
@@ -137,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.
@@ -172,8 +167,7 @@
section. Each string is null terminated.
-
-
+
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
@@ -212,15 +206,14 @@
e.g., booleans, then numbers and finally strings.
-
-
- 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,
@@ -238,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:
@@ -276,25 +268,21 @@
-
-
+
Some limitations: total compiled entries cannot exceed
4096 bytes. The name field cannot exceed 128 bytes.
-
-
+
/usr/share/terminfo/*/* compiled terminal capability data
base
-
-
+
curses(3x), terminfo(5).
-
-
+
Thomas E. Dickey
extended terminfo format for ncurses 5.0
hashed database support for ncurses 5.6