Innocenti Maresin <[EMAIL PROTECTED]> $B$5$s$O=q$-$^$7$?(B:
(B
(B> On a *good* Linux [...] should "unicode_stop" change keymap properly?
(B
(BI also noticed recently, that "unicode_stop" doesn't change
(Bthe keymap back to the state it was before calling "unicode_start".
(B
(B"unicode_start" contains:
(B
(B # Change the keyboard mapping in such a way that the non-ASCII keys
(B # produce UTF-8 encoded multibyte sequences, instead of single bytes
(B # >= 0x80 in a legacy 8-bit encoding.
(B
(B dumpkeys | loadkeys --unicode
(B
(Bbut "unicode_stop" contains nothing to revert this, i.e.
(Bafter calling
(B
(B unicode_start
(B unicode_stop
(B
(Bnon ASCII characters (e.g. German umlauts) still appear as UTF-8
(Bsequences on the console.
(B
(BIs there a way to revert the effect of "dumpkeys | loadkeys --unicode"
(Bor does one really have to reload the original keymap again with
(B"loadkeys"?
(B
(B--
(BMike Fabian <[EMAIL PROTECTED]> http://www.suse.de/~mfabian
$B?gL2ITB-$O$$$$;E;v$NE([EMAIL PROTECTED](B
(B--
(BLinux-UTF8: i18n of Linux on all levels
(BArchive: http://mail.nl.linux.org/linux-utf8/
