+ This is the scheme used in System V, which legacy Unix
+ systems use, and the <STRONG>TERMINFO</STRONG> variable is used by
+ <EM>curses</EM> applications on those systems to override the
+ default location of the terminal database.
+
+ <STRONG>o</STRONG> If <STRONG>ncurses</STRONG> is built to use hashed databases, then each
+ entry in this list may be the path of a hashed data-
+ base file, e.g.,
+
+ /usr/share/terminfo.db
+
+ rather than
+
+ /usr/share/terminfo/
+
+ The hashed database uses less disk-space and is a lit-
+ tle faster than the directory tree. However, some
+ applications assume the existence of the directory
+ tree, reading it directly rather than using the ter-
+ minfo library calls.
+
+ <STRONG>o</STRONG> If <STRONG>ncurses</STRONG> is built with a support for reading termcap
+ files directly, then an entry in this list may be the
+ path of a termcap file.
+
+ <STRONG>o</STRONG> If the <STRONG>TERMINFO</STRONG> variable begins with "hex:" or "b64:",
+ <STRONG>ncurses</STRONG> uses the remainder of that variable as a com-
+ piled terminal description. You might produce the
+ base64 format using <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>:
+
+ TERMINFO="$(infocmp -0 -Q2 -q)"
+ export TERMINFO
+
+ The compiled description is used if it corresponds to
+ the terminal identified by the <STRONG>TERM</STRONG> variable.
+
+ Setting <STRONG>TERMINFO</STRONG> is the simplest, but not the only way to
+ set location of the default terminal database. The com-
+ plete list of database locations in order follows:
+
+ <STRONG>o</STRONG> the last terminal database to which <STRONG>ncurses</STRONG> wrote,
+ if any, is searched first
+
+ <STRONG>o</STRONG> the location specified by the TERMINFO environment