Documentation for the AT&T Sceptre Videotex terminal

I would dispote the 'most' The keyboards I have here fall into 3 main cetegories 1) A simple matrix of switches to be scanned by the main processor (common on home micros). This matrix _may_ be laid out so that the row/column number ofa key is related in some simple way to the character code, BTW. 2) Keyboards that are hardware encoded to output the final character codes (normally ASCII). 3) KEyboards that are hardware encoded to send a keycode that has little relationship to the character code. In general, if you have versions of (3) fro different (human) languages, a given key postion will send the same keycode, no matter what appears on the keycap.. No wait a second. Does it actually matter for the purposes of this discussion what the actual communcation is between a VT100 and its keyboard? Assuming you're not going to modify the VT100's firmware (if you're allowing modificatations then _anything_ is possible ;-)), a VT100 sends a particular code out of its serial port when you press a key (subject othe modifier keys, SHIFT, etc). The fact that (IIRC) the keyboard sends a keycode over the seiral interface to the VT100 mainboard, and it's turned into ASCII by the firmware doesn't make any diffference IMHO as to whether, for example, this keyboard can be considered to be an upper-case only one or an upper/lower case one. Rememebr them? I use one... Well, for the typewriter I have, each key/type hammer is an independant mechanism. Pressing a key activates the type hammer it's linked to. No encoding/decoding at all. -tony