Termcap Standardization

[Peter da Silva]

>   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!

K10 is not a valid TERMCAP feild name. KA is key 10. If you find a K10 in
the entry you'ld do well to get it changed, as it will break many a program,
not mine, but many others.

>   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

Terminal graphics are really outside the scope of Termcap. Terminfo can
probably handle them, but Termcap was never designed to deal with anything
but BL through TILDE.

>   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.

If people find your programs useful they will be able to set up their own
TERMCAP file to deal with them: "setenv TERMCAP $HOME/termcap". It is probably
inadvisable to require graphics character sets in a termcap program, as many
terminals don't support them... certainly damn few terminal emulators do.

Or you could go with curses/terminfo... speaking of which: does anybody nearby
baylor or hyd-ptd have the PD curses/terminfo source lying around?
-- 
	Peter da Silva (the mad Australian werewolf)
		UUCP: ...!shell!neuro1!{hyd-ptd,baylor,datafac}!peter
		MCI: PDASILVA; CIS: 70216,1076