Yeah, that makes sense.
>(And indeed, one might argue that there should be a test for VC_UNICODE
>before UTF-8 is generated; if I recall correctly, I left the test in a comment,
>since it is ugly to generate error messages from the keyboard driver.)
>Since your application is Unicode-aware, it takes only one ioctl to tell
>that to the kernel.
OK, I'll just go ahead and do that--the library already saves the keyboard
mode anyway so that it can restore it from VC_MEDIUMRAW mode. I really
didn't intend for this to become such a big deal, BTW; I was just asking
for the motivation for the check in the ioctl because it didn't seem
completely logical at first.
Also BTW: the library will be LGPLed; although I'm not sure when it'll
be ready (my schedule's a tad busy for at least the next 6 weeks), I'd love
to have you alpha test it when I get to that stage (if you wouldn't mind,
that is).
-- Aaron Ucko (ucko@vax1.rockhurst.edu; finger for PGP public key) | httyp!
"That's right," he said. "We're philosophers. We think, therefore we am."
-- Terry Pratchett, _Small Gods_ | Geek Code 3.1 [for explanation, finger
hayden@mankato.msus.edu]: GCS/M/S/C d- s: a18 C++(+++)>++++ UL++>++++ P++
L++>+++++ E- W(-) N++(+) o+ K- w--- O M@ V-(--) PS++(+++) PE- Y(+) PGP(+) t(+)
!5 X-- R(-) tv-@ b++(+++) DI+ !D-- G++(+++) e->+++++(*) h!>+ r-(--)>+++ y?