captoinfo(1m)
_________________________________________________________________
captoinfo
convert a termcap description into a terminfo description
_________________________________________________________________
SYNTAX
captoinfo [-v ...] [-V] [-1] [-w width] [file] ...
DESCRIPTION
captoinfo looks in file for termcap(5) descriptions. For each
one found, an equivalent terminfo(4) description is written to
standard output, along with any comments found. A description
which is expressed as relative to another description (as
specified in the termcap tc = field) will be reduced to the
minimum superset before being output.
If no file is given, then the environment variable TERMCAP is
used for the filename or entry. If TERMCAP is a full pathname to
a file, only the terminal whose name is specified in the
environment variable TERM is extracted from that file. If the
environment variable TERMCAP is not set, then the file
/etc/termcap is read.
OPTIONS
-v print out tracing information on standard error as the
program runs. Specifying an additional -v option will
cause more detailed information to be printed.
-V print out the version of the program in use on standard
error and exit.
-1 cause the fields to print out one to a line.
Otherwise, the fields will be printed several to a line
to a maximum width of 60 characters.
-w change the maximum output width to width characters.
FILES
/usr/lib/terminfo/?/* compiled terminal description database
/etc/termcap old, textual terminal description database
DG/UX 4.00 Page 1
Licensed material--property of copyright holder(s)
captoinfo(1m)
WARNINGS
Certain termcap defaults are assumed to be true. For example,
the bell character (terminfo bel) is assumed to be ^G. The
linefeed capability (termcap nl) is assumed to be the same for
both cursor_down and scroll_forward (terminfo cud1 and ind,
respectively.) Padding information is assumed to belong at the
end of the string.
The algorithm used to expand parameterized information for
termcap fields such as cursor_position (termcap cm, terminfo cup)
will sometimes produce a string which, though technically
correct, may not be optimal. In particular, the rarely used
termcap operation %n will produce strings that are especially
long. Most occurrences of these non-optimal strings will be
flagged with a warning message and may need to be recoded by
hand.
The short two-letter name at the beginning of the list of names
in a termcap entry, a hold-over from an earlier version of the
termcap convention, will be deleted.
DIAGNOSTICS
tgetent failed with return code n (reason).
The termcap entry is not valid for the specified
reason. In particular, check for an invalid 'tc='
entry.
commented out code cc is unknown.
An unknown commented out termcap code cc was specified.
unknown type given for the termcap code cc.
The termcap description had an entry for cc whose type
was not boolean, numeric, or string.
cc.
wrong type given for the boolean (numeric, string) termcap code
The termcap entry cc was entered as a capability of the
wrong type; for instance, a boolean entry was entered
as a numeric capability.
the boolean (numeric, string) termcap code cc is not a valid
name. An unknown termcap code was specified.
cap cc (info ii) is NULL: REMOVED
The termcap code was specified as a null string. The
correct way to cancel an entry is with an @, as in
:bs@:. Giving a null string could cause incorrect
DG/UX 4.00 Page 2
Licensed material--property of copyright holder(s)
captoinfo(1m)
assumptions to be made by the software which uses
termcap or terminfo.
obsolete 2 character name ss removed. Synonyms are string.
An obsolete two-letter terminal name in the current
termcap entry was not propagated into the terminfo
entry.
already has the value vv2.
a function key for cc was specified with the value vv1, but it
When parsing the ko capability, the key cc was
specified as having the same value as the capability
vv1, but the key cc already had the value vv2.
capability.
the unknown termcap name cc was specified in the `ko' termcap
A key was specified in the ko capability which could
not be handled.
the vi character v (info ii) has the value xx, but `ma' gives n.
The ma capability specified a function key with a value
different from that specified in another setting of the
same key.
the unknown vi key v was specified in the ma termcap capability.
A key unknown to captoinfo was specified in the ma
capability.
Warning: termcap sg and ug had different values (nn1<->nn2).
terminfo assumes that the sg (now xmc) and ug values
were the same.
Warning: the string produced for ii may be inefficient.
The parameterized string being created should be
rewritten by hand.
Null termname given.
The terminal type was null. This is printed if the
environment variable TERM is not set or is null.
cannot open file for reading.
The specified file could not be opened.
SEE ALSO
infocmp(1M), tic(1M).
curses(3X), terminfo(4), termcap(5) in the Programmer's Reference
for the DG/UX System.
DG/UX 4.00 Page 3
Licensed material--property of copyright holder(s)
captoinfo(1m)
Chapter 7 in Programmer's Guide to the DG/UX System.
NOTES
captoinfo should be used to convert termcap(5) entries to
terminfo(4) entries because programs that use curses(3X) depend
upon terminfo(4).
DG/UX 4.00 Page 4
Licensed material--property of copyright holder(s)