X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fterm.5.html;h=1f70937c3d33d29e08d3da08a65214371d037428;hp=34b904a13eb10fba604aa2fd36b11ce4ed2f5bbc;hb=d90067f9008bb8338a77c1ed519bc108c275ed04;hpb=b97ea58e03d5faebed2166faa4e0e590f2cdea34 diff --git a/doc/html/man/term.5.html b/doc/html/man/term.5.html index 34b904a1..1f70937c 100644 --- a/doc/html/man/term.5.html +++ b/doc/html/man/term.5.html @@ -28,19 +28,19 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: term.5,v 1.67 2023/12/02 20:49:04 tom Exp @ + * @Id: term.5,v 1.68 2023/12/16 20:32:22 tom Exp @ -->
-term(5) File formats term(5) @@ -60,7 +60,7 @@
Compiled terminfo descriptions are placed under the directory /usr/share/terminfo. Two configurations are supported (when building - the ncurses libraries): + the ncurses libraries): directory tree A two-level scheme is used to avoid a linear search of a huge Unix @@ -76,12 +76,12 @@ with the terminfo's primary name as a key, and records containing only aliases pointing to the primary name. - If built to write hashed databases, ncurses can still read + If built to write hashed databases, ncurses 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. - ncurses distinguishes the two cases in the TERMINFO and + ncurses 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. @@ -192,11 +192,11 @@ binary format is used in all modern Unix systems. Each system uses a predefined set of boolean, number or string capabilities. - The ncurses libraries and applications support extended terminfo binary + The ncurses libraries and applications support extended terminfo binary format, allowing users to define capabilities which are loaded at runtime. This extension is made possible by using the fact that the other implementations stop reading the terminfo data when they have - reached the end of the size given in the header. ncurses checks the + reached the end of the size given in the header. ncurses checks the size, and if it exceeds that due to the predefined data, continues to parse according to its own scheme. @@ -215,7 +215,7 @@ The count- and size-values for the extended string table include the extended capability names as well as extended capability values. - Using the counts and sizes, ncurses allocates arrays and reads data for + Using the counts and sizes, ncurses allocates arrays and reads data for the extended capabilities in the same order as the header information. The extended string table contains values for string capabilities. @@ -223,10 +223,10 @@ extended capabilities in order, e.g., booleans, then numbers and finally strings. - By storing terminal descriptions in this way, ncurses is able to + By storing terminal descriptions in this way, ncurses is able to provide a database useful with legacy applications, as well as providing data for applications which need more than the predefined - capabilities. See user_caps(5) for an overview of the way ncurses uses + capabilities. See user_caps(5) for an overview of the way ncurses uses this extended information. Applications which manipulate terminal data can use the definitions @@ -235,7 +235,7 @@
- On occasion, 16-bit signed integers are not large enough. With ncurses + On occasion, 16-bit signed integers are not large enough. With ncurses 6.1, a new format was introduced by making a few changes to the legacy format: @@ -288,7 +288,7 @@ This implementation is by default compatible with the binary terminfo format used by Solaris curses, except in a few less-used details where it was found that the latter did not match X/Open Curses. The format - used by the other Unix versions can be matched by building ncurses with + used by the other Unix versions can be matched by building ncurses with different configuration options. @@ -312,13 +312,13 @@
A small number of terminal descriptions use uppercase characters in their names. If the underlying filesystem ignores the difference - between uppercase and lowercase, ncurses represents the "first + between uppercase and lowercase, ncurses represents the "first character" of the terminal name used as the intermediate level of a directory tree in (two-character) hexadecimal form.
- ncurses stores compiled terminal descriptions in three related formats, + ncurses stores compiled terminal descriptions in three related formats, described in the sections o LEGACY STORAGE FORMAT, and @@ -329,7 +329,7 @@ The legacy storage format and the extended number format differ by the types of numeric capability which they can store (i.e., 16-bit versus - 32-bit integers). The extended storage format introduced by ncurses + 32-bit integers). The extended storage format introduced by ncurses 5.0 adds data to either of these formats. Some limitations apply: @@ -387,9 +387,9 @@
Thomas E. Dickey - extended terminfo format for ncurses 5.0 - hashed database support for ncurses 5.6 - extended number support for ncurses 6.1 + extended terminfo format for ncurses 5.0 + hashed database support for ncurses 5.6 + extended number support for ncurses 6.1 Eric S. Raymond documented legacy terminfo format, e.g., from pcurses. @@ -400,7 +400,7 @@ -ncurses 6.4 2023-12-02 term(5) +ncurses 6.4 2023-12-16 term(5)