The syntax of the Compose mechanism in loadkeys can't seem to do the
decimal byte values 0 or 10, and there don't seem to be any kernel
keyboard driver action names for the hex values 0x80 through 0x9f. With
a large number of accent table slots, the usual regional characters
can be supported in addition to the hexpad interface. Also, in 1999
terms, compose key slots are very cheap. As cheap as they are, I'll
probably do upper and lowercase A-F's, plus move the ISO-blabla
keys up above that.
In other words, a hexpad is pure mechanism, where other interfaces have
a policy component. A hexpad is one of those things you hope to never
need, but you don't want to be without. The userspace implementation
that caused me to bump into MAX_DIACR is Left As An Excersize To The
Reader.
Rick Hohensee
cLIeNUX hexhead
About a previous error, in my character frequencies post, Jes Sorensen
pointed out that there are 8-bit characters in the kernel sources, and
indeed there do seem to be, at least in the kernel defkeymap.c or whatever
the name is. I suspect the basic proportions of the characters in that
post were close though.
-
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/