> Yes, this all true. But is symbols which not display correctly
> needed on keyboard ?
Probably rarely, but fonts that share glyphs among multiple characters
have much sense. Keyboard-to-application mapping is independent from
application-to-screen mapping. There is no reason to restrict inputtable
characters to those that are uniquely outputtable. It gives completely no
advantage and does have bad effects - the only reason is our laziness.
> And add to console driver one another screen buffer in which will be
> stored unicode symbols.
And this is another thing; it could give correct gpm pasting when using
fonts that share glyphs. Unicoded screen buffer is not needed for proper
keyboard translation, but would have its own advantage.
--
__("< Marcin Kowalczyk * qrczak@knm.org.pl http://kki.net.pl/qrczak/
\__/ GCS/M d- s+:-- a21 C+++>+++$ UL++>++++$ P+++ L++>++++$ E->++
^^ W++ N+++ o? K? w(---) O? M- V? PS-- PE++ Y? PGP->+ t
QRCZAK 5? X- R tv-- b+>++ DI D- G+ e>++++ h! r--%>++ y-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/