HP-UX Reference (11i v1 05/09) - 4 File Formats (vol 8)

t
terminfo(4) terminfo(4)
(ENHANCED CURSES)
rest_of_feature_line : features COMMA NEWLINE
| COMMA NEWLINE
;
features : COMMA feature
| features COMMA feature
;
aliases : PIPE ALIAS
| aliases PIPE ALIAS
;
feature : BOOLEAN
| NUMERIC
| STRING
;
(1) An ALIAS that begins in column one. This is handled by the lexical analyzer.
(2) A BOOLEAN feature that begins after column one but is the first feature on the feature line.
This is handled by the lexical analyzer.
(3) A NUMERIC feature that begins after column one but is the first feature on the feature line.
This is handled by the lexical analyzer.
(4) A STRING feature that begins after column one but is the first feature on the feature line. This
is handled by the lexical analyzer.
The lexical conventions for terminfo descriptions are as follows:
1. White space consists of the <space> and <tab> characters.
2. An ALIAS may contain any graph characters other than comma (,), slash (/), and bar (|).
(Graph characters are those characters for which isgraph() returns nonzero; see ctype(3C).)
3. A LONGNAME may contain any print characters other than comma (,) and bar (|). (Print char-
acters are those characters for which isprint() returns nonzero; see ctype(3C).)
4. A BOOLEAN feature may contain any print characters other than comma (,), equals (=), and
pound sign (#).
5. A NUMERIC feature consists of:
a. A name which may contain any print character other than comma (,), equals (=), and
pound sign (#).
b. The pound sign (#) character.
c. A positive integer which conforms to the C language convention for integer constants.
6. A STRING feature consists of:
a. A name which may contain any print character other than comma (,), equals (=), and
pound sign (#).
b. The equals (=) character.
c. A string which may contain any print characters other than comma (,).
7. White space immediately following a comma (,) is ignored.
8. Comments consist of the beginning of a line, optional white space, a required pound sign (#), and
a terminating end of line.
9. A header line must begin in column one.
10. A feature line must not begin in column one.
11. Blank lines are ignored.
Defined Capabilities
X/Open defines the capabilities listed in the following table. All X/Open-compliant implementations must
accept each of these capabilities in an entry in a terminfo source file. Implementations use this informa-
tion to determine how properly to operate the current terminal. In addition, implementations return any
of the current terminal’s capabilities when the application calls the query functions listed in tgetent() (in
HP-UX 11i Version 1: September 2005 − 3 − Hewlett-Packard Company Section 4−−329