untranslated keyboard

[totaam]

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 #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.

[totaam]

See also #1062, #1171.

[totaam]

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:

• extend this to shadow servers (win32 and osx)
• maybe support X11 server layout changes: re-detect updated settings
• maybe have an "auto" mode for enabling this when both ends are compatible? (ie: win32 shadow server with win32 client, X11 client with X11 server)
• maybe disable or remove the tray menu for cases where it won't be applicable

[totaam]

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

[totaam]

See also #2560, #2561, #1716