From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60530) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XwMEG-0002pQ-Ph for qemu-devel@nongnu.org; Wed, 03 Dec 2014 21:33:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XwMEA-0000Bb-Kq for qemu-devel@nongnu.org; Wed, 03 Dec 2014 21:33:16 -0500 Received: from szxga03-in.huawei.com ([119.145.14.66]:48457) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XwMEA-0000B8-1u for qemu-devel@nongnu.org; Wed, 03 Dec 2014 21:33:10 -0500 Message-ID: <547FC7C8.6050304@huawei.com> Date: Thu, 4 Dec 2014 10:32:40 +0800 From: Gonglei MIME-Version: 1.0 References: <1417589746-12176-1-git-send-email-arei.gonglei@huawei.com> <20141203093807.GA10160@redhat.com> <547EDD01.7050608@huawei.com> <1417608638.14168.49.camel@nilsson.home.kraxel.org> In-Reply-To: <1417608638.14168.49.camel@nilsson.home.kraxel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard layout dynamically List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: "Huangweidong (C)" , "lcapitulino@redhat.com" , "qemu-devel@nongnu.org" , "Huangpeng (Peter)" On 2014/12/3 20:10, Gerd Hoffmann wrote: > 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. > I see, great thanks for your explanation, Gerd :) > 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. > Hum.. Now, I encountered this situation that the common clienteles just use tightvnc client, but want to change keymap dynamically. As you say, the only way address this scenario is doing it on the server side. So, do you think this patch series make sense and consider to accept it in upstream? Thanks! Regards, -Gonglei