Xpra: Ticket #1172: untranslated keyboard

Follow up from #1099. We should just pass the raw scancode to the server when we know it will be able to handle it. ie: win32 client with win32 server.

Also, expand r12399 to support more characters - generate the list? (deal non ascii characters too)

Think about better handling for keyboard layout mismatch between client and server, see ticket:1099#comment:10. We could keep multiple translation tables for each layout in use, then use the correct translation for the currently active keyboard layout. See #1027, #817.

Sun, 17 Apr 2016 02:58:45 GMT - Antoine Martin: status changed

See also #1062, #1171.

Sat, 23 Apr 2016 05:15:30 GMT - Antoine Martin: description changed

Tue, 12 Jul 2016 16:52:22 GMT - Antoine Martin: milestone changed

Milestone renamed

Sat, 13 Aug 2016 10:07:45 GMT - Antoine Martin: summary changed

Initial support in r13328: I can attach an X11 client to an X11 server with --keyboard-layout=fr --keyboard-raw=yes and get a 'fr' layout even though my local keymap is set to 'gb'. The raw keycodes are used unmodified by the server.

Still TODO:

Sat, 29 Sep 2018 08:52:39 GMT - Antoine Martin: milestone changed

Rather than extending the key packet with yet more data, we could use #1942 (new packet format).

Sun, 04 Aug 2019 03:57:53 GMT - Antoine Martin: milestone changed

Thu, 23 Jan 2020 08:32:28 GMT - totaamwin32:

See also #2560, #2561, #1716

Wed, 12 Feb 2020 05:12:24 GMT - Antoine Martin: milestone changed

Sat, 23 Jan 2021 05:16:56 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1172