[BRLTTY] linux screen driver and commands

Samuel Thibault samuel.thibault at ens-lyon.org
Fri Mar 10 03:50:42 EST 2006


Yannick PLASSIARD, le Fri 10 Mar 2006 09:35:04 +0100, a écrit :
> 1) Where are those KEY_ defined ?

/usr/include/linux/input.h

_NOTA_: KEY_A does not mean "the key on which an 'A' is printed". It
means "the key on which 'A' is printed on a qwerty keyboard", i.e. it is
always the first key of the second row on the physical keyboard,
whatever the keyboard layout.

> 2) Is this switch-case dependent of the "local keyboard papping (such
> as azerty, qwerty, and so on?) because it seems to be a qwerty map
> into the screen.c file?

Yes. This is a well-known default mapping.

> And if so, what happens for accent - keys such as E acute, a grave; and so on ?

They won't work that this function.

But this doesn't pose problem: in XLATE or UNICODE mode (i.e. the usual
mode), all textual keypresses are always emulated by the insertByte
function (insertUinputKey() is only used for special key combination
that can't be simulated by TIOCSTI). In RAW or MEDIUMRAW modes, this is
not the case. In such case, the keyboard mapping will be qwerty ; but in
practice, these modes are only used by X, for which xbrlapi is able to
directly simulate correct keypresses in the X server.

Nota: since evdev also provides KEY_* codes, you can simulate them back
using the currently implemented uinput facility, you don't need to care
about keyboard mapping.

Regards,
Samuel


More information about the BRLTTY mailing list