X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fterm.5.html;h=5fab776ded8c8d9f380cea55fffacc98be990b05;hp=4d1679e3a25d2c6015f7e1a4c22b6d8263e7795b;hb=9193d076200365eeb5ff932acdbbdcc5e452292c;hpb=17c5992a16be94247b83f2bbb9accdd9b7e7bb72
diff --git a/doc/html/man/term.5.html b/doc/html/man/term.5.html
index 4d1679e3..5fab776d 100644
--- a/doc/html/man/term.5.html
+++ b/doc/html/man/term.5.html
@@ -1,6 +1,6 @@
@@ -34,7 +34,7 @@
term 5
-
+
@@ -200,7 +200,7 @@
6.1, a new format was introduced by making a few changes to the legacy
format:
- o a different magic number (0542)
+ o a different magic number (octal 01036)
o changing the type for the number array from signed 16-bit integers
to signed 32-bit integers.
@@ -213,6 +213,8 @@
Note that it is possible for setupterm to expect a different set of
capabilities than are actually present in the file. Either the data-
base may have been updated since setupterm has been recompiled (result-
@@ -223,6 +225,12 @@
new capabilities must always be added at the end of the lists of bool-
ean, number, and string capabilities.
+
+
+ X/Open Curses does not specify a format for the terminfo database.
+ UNIX System V curses used a directory-tree of binary files, one per
+ terminal description.
+
Despite the consistent use of little-endian for numbers and the other-
wise self-describing format, it is not wise to count on portability of
binary terminfo entries between commercial UNIX versions. The problem
@@ -233,11 +241,31 @@
terminfo(5) for detailed discussion of terminfo source compatibility
issues.
+ 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
+ different configuration options.
+
+
+
+ The magic number in a binary terminfo file is the first 16-bits (two
+ bytes). Besides making it more reliable for the library to check that
+ a file is terminfo, utilities such as file also use that to tell what
+ the file-format is. System V defined more than one magic number, with
+ 0433, 0435 as screen-dumps (see scr_dump(5)). This implementation uses
+ 01036 as a continuation of that sequence, but with a different high-
+ order byte to avoid confusion.
+
+
+
Direct access to the TERMTYPE structure is provided for legacy applica-
tions. Portable applications should use the tigetflag and related
functions described in curs_terminfo(3x) for reading terminal capabili-
ties.
+
+
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 charac-
@@ -329,7 +357,15 @@