It appears that both the input method and the client have to do the xkb
decoding from hardware events to keysyms and shift information. And that
the method used by the input method to produce "other" keys is to, in
effect, run xkb backwards to produce fake hardware events from the
desired resul
On Mon, Nov 05, 2012 at 03:26:38AM +0100, Jan Arne Petersen wrote:
> From: Jan Arne Petersen
>
> Hardware keyboard input allows input methods to grab the keyboard
> and process hardware key events to generate text events (with
> pre-edit) over the same text_model interface we use for the virtual
From: Jan Arne Petersen
Hardware keyboard input allows input methods to grab the keyboard
and process hardware key events to generate text events (with
pre-edit) over the same text_model interface we use for the virtual
keyboard. This allows input methods which compose multiple key
events for inp
