ncurses 6.4 - patch 20231223

[ncurses.git] / man / term.5

diff --git a/man/term.5 b/man/term.5
index e1eaa995e1d813f3a2d29aceb8a0efcbcdd17f57..ede2eb1c285de0a3eac021255dbb32d5b3e0b7cd 100644 (file)
--- a/man/term.5
+++ b/man/term.5
@@ -28,8 +28,8 @@
 .\" authorization.                                                           *
 .\"***************************************************************************
 .\"
-.\" $Id: term.5,v 1.68 2023/12/16 20:32:22 tom Exp $
-.TH term 5 2023-12-16 "ncurses 6.4" "File formats"
+.\" $Id: term.5,v 1.69 2023/12/23 16:08:25 tom Exp $
+.TH term 5 2023-12-23 "ncurses 6.4" "File formats"
 .ie \n(.g \{\
 .ds `` \(lq
 .ds '' \(rq
@@ -62,7 +62,7 @@ compiled \fIterminfo\fR terminal description
 .SH SYNOPSIS
 .B term
 .SH DESCRIPTION
-.SS STORAGE LOCATION
+.SS "Storage Location"
 Compiled terminfo descriptions are placed under the directory \fB\*d\fP.
 Two configurations are supported
 (when building the \fI\%ncurses\fP libraries):
@@ -97,7 +97,7 @@ It can write (or rewrite) entries in the hashed database.
 \fI\%TERMINFO_DIRS\fP environment variable by assuming a directory tree
 for entries that correspond to an existing directory,
 and hashed database otherwise.
-.SS LEGACY STORAGE FORMAT
+.SS "Legacy Storage Format"
 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.
@@ -215,7 +215,7 @@ Special characters in \*^X or \ec notation are stored in their
 interpreted form, not the printing representation.
 Padding information $<nn> and parameter information %x are
 stored intact in uninterpreted form.
-.SS EXTENDED STORAGE FORMAT
+.SS "Extended Storage Format"
 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 modern Unix systems.
@@ -276,7 +276,7 @@ Applications which manipulate terminal data can use the definitions
 described in \fBterm_variables\fP(3X) which associate the long capability
 names with members of a \fBTERMTYPE\fP structure.
 .
-.SS EXTENDED NUMBER FORMAT
+.SS "Extended Number Format"
 On occasion, 16-bit signed integers are not large enough.
 With \fI\%ncurses\fP 6.1,
 a new format was introduced by making a few changes
@@ -315,7 +315,7 @@ 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, number, and string capabilities.
-.SS Binary format
+.SS "Binary Format"
 X/Open Curses does not specify a format for the terminfo database.
 System V curses used a directory-tree of binary files,
 one per terminal description.
@@ -338,7 +338,7 @@ 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 \fI\%ncurses\fP
 with different configuration options.
-.SS Magic codes
+.SS "Magic Codes"
 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,
@@ -347,12 +347,12 @@ System V defined more than one magic number,
 with 0433, 0435 as screen-dumps (see \fBscr_dump\fP(5)).
 This implementation uses 01036 as a continuation of that sequence,
 but with a different high-order byte to avoid confusion.
-.SS The TERMTYPE structure
+.SS "The \fITERMTYPE\fP Structure"
 Direct access to the \fBTERMTYPE\fP structure is provided for legacy
 applications.
 Portable applications should use the \fBtigetflag\fP and related functions
 described in \fBcurs_terminfo\fP(3X) for reading terminal capabilities.
-.SS Mixed-case terminal names
+.SS "Mixed-case Terminal Names"
 A small number of terminal descriptions use uppercase characters in
 their names.
 If the underlying filesystem ignores the difference between