Termcap Standardization

[Robin Cutshaw]

I have been working on a set of programs that make heavy use of function keys
and cursor motion keys if they are available.  Using the termlib stuff for
termcap is proving to be useless.

  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.
There seems to be no way to get them all covered!

  The line drawing character set definitions are equally confused.  Many
termcap entries just don't define characters that are there at all, and
some leave out entries like GC, GL, and GR.  Many terminals that have the
single line drawing character set also have the double line and double-single
line sets also, but there is no definition mechanism in termcap.

  In general, there are many ommisions and errors in the termcap database.  I
thought about using the termcap compare program posted not too long ago, but
this doesn't help others who might like to use my programs.

PROPOSAL :

  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.

  It doesn't seem to be an impossible task.  Does terminfo have such problems?

-- 
----
Robin Cutshaw
uucp:   ...!{akgua,gatech}!medstar!robin