Termcap Standardization

[Doug Gwyn <gwyn>]

>   It seems that function key definitions (k0-k9) are used differently for
> various terminals.  Some entries use k0 for function key #1 and k9 for
> function key #10 (e.g. visual, tvi920, altos), whereas some use k1 for
> key #1 and k0 for key #10 (most others).  Also, some terminals with more
> than 10 function keys use kA, kB, etc. while some use k10, k11, k12, etc.

k10.. definitely will not work; termcap capability names are limited to two
characters.  Many of the two-letter combinations starting with k are
already reserved for other keys (kb = backspace, etc.).  The first function
key should be "k0" but as you note many termcaps start at "k1".  You can
overcome this in your application by trying to get strings for k0..k9
and corresponding labels l0..l9, using whatever you found rather than
making any assumptions about them.

>   The line drawing character set definitions are equally confused.

There are no standard line-drawing capabilities in termcap or terminfo.
(There is no support for graphics, either.  This is by design.)

>   In general, there are many ommisions and errors in the termcap database.

Yes, indeed.  (Spelling errors, too.)

>   A standard termcap from a single source with version support and terminal
> entry submission and screening.  This doesn't have to break anything already
> there, it would just standardize for everyone (app developers and end users)
> a database that is well defined and supposedly correct.  Granted, this would
> be a monumental task at first, but as standard termcaps settled down it
> wouldn't be to difficult.

You could send your contributions to Berkeley or to me at BRL so that
future shipments of our systems would include your entries.  Remember
that this is all volunteer labor.

> Does terminfo have such problems?

The only reason terminfo is in better overall shape is that it is
relatively new and was provided by a single source.