When doing some experimenting with the acm/screen maps I discovered some strange things, as to not-working and vice-versa-working. And I would need an advice where to hook in for fixing, please.
system information: - running linux-2.4.10, compiled with/against 2.4.5 - kbd-1.06, ncurses-5.2 state after system start: - with matrox fb - with keymap de-latin-nodeadkeys - without font loading/changing - and $TERM=linux - and dumpkeys saying 0x000f=control_o 0x000e=control_n - and inputrc allowing 8-bits - and locale charmap as ISO-8859-1 expected behaviour from this: - G0 set to default latin1 and G1 set to VT100 graphics - typing [Ctrl]+[o] sending Control_o (switch to G0) - typing [Ctrl]+[n] sending Control_n (switch to G1) here is what happens in reality: docs hit keys echo -e orders SI=G0=^O [Ctrl]+[o] \\033o \\x1bo \\x0e \\016 SO=G1=^N [Ctrl]+[n] \\033n \\x1bn \\x0f \\017 results negative neg. neg. both switched Ctrl+o looks like CR is sent; Ctrl+n beeps \\033o \\x1bo and according n's don't show any change \\x0e \\016 look like switched to G1 VT100 graphics \\x0f \\017 look like switched to G0 latin1 So only echoing the hex/oct values seem to get at least the G0/G1 maps -- only that they now are just the other way round than it should be. And there seems to be no program to report the status (like say, tty2: using G0, currently set to latin1) so I can only judge from what I see. I guess the keymap will need change to make the key-hitting work the way it should be, but what do I check for the vice-versa 0e/0f signal? Thanks for your comments. -- Erika Pacholleck <[EMAIL PROTECTED]> for private replies unhex my last name -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
