Windows Host / Sway Client: Keyboard prints wrong characters

[Telkhine]

What works

• Mouse works fine. Left click, right click and mouse wheel all tested fine.
• copy/paste works as well, both from host to client and client to host.

What doesn't work

The keymap translation between my Windows host and Sway client seems to be messed up. a becomes u, s becomes i, etc.

On the linux/sway side, I ran setxkbmap -print > ~/.config/waynergy/xkb_keymap, which gives:

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};

I use a standard 105 key US keyboard. Nothing fancy. Is there anything on windows that I would need to change? Is windows even supported here?

EDIT:
On the host I'm running barrier 2.3.3

[r-c-f]

For UNIXy platforms it's been easier to pass the raw scancodes and let xkb use the pre-existing mappings; this is probably a good reason to see if xkb will tolerate an xkb_keycodes section using the platform-agnostic Synergy key IDs at some point in the next few days.

[r-c-f]

...and indeed writing an xkb mapping to accept arbitrary UTF32 is probably not going to happen. However, using
this keycodes section does work for me -- with that in ~/.xkb/keycodes/win and

xkb_keymap {
	xkb_keycodes  { include "win+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};

as the keymap configuration I was able to get it to work with a Windows primary. Some keys are missing (I don't actually own a working full-sized keyboard it would seem) but the relevant keycodes can be found in wev or xev or the like.

[Telkhine]

That seems to work. Thanks for the assist!

EDIT:
For posterity: The right arrow key wasn't working, so I had to change the <RIGHT> symbol to <RGHT>, which I was able to figure out by looking at /usr/share/X11/xkb/symbols/inet.

[r-c-f]

@dankles I've added a slightly more complete one as https://github.com/r-c-f/waynergy/blob/master/doc/xkb/keycodes/win which fixed that as well as the numpad.

[char]

This works, but it still emits the wrong characters if you're typing into an XWayland window for some reason :(

[r-c-f]

I've updated the example windows key map to use an offset of 7, which should placate X.