Hi, > Hi, Daniel > Actually, my team had received the requirement of changing VNC keyboard > layout dynamically on the scenario of Desktop Cloud. The clientele just use > the simplest tight vnc client, but not GTK-VNC etc. I think we should support > this scenario, isn't it ?
It boils down to doing the keysym -> scancode translation on the server side (tightvnc client, qemu vnc server needs -k) or on the client side (anything gtk-vnc based, such as virt-viewer / remote-viewer or vinagre (gnome vnc viewer)). The big advantage of doing it on the client side (then send the scancodes using the scancode extension as mentioned by Daniel) is that it works without any manual configuration, and you can even have two vnc clients with different local keymaps connected at the same time and things are still working properly. In case the client can't do the translation qemu will fallback to do it on the server side. It's not the recommended way to operate though. cheers, Gerd
