From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52822)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Xw8lm-0006d8-QO
	for qemu-devel@nongnu.org; Wed, 03 Dec 2014 07:11:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Xw8lg-0003xf-G1
	for qemu-devel@nongnu.org; Wed, 03 Dec 2014 07:10:58 -0500
Received: from mx1.redhat.com ([209.132.183.28]:46321)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Xw8lg-0003xO-8M
	for qemu-devel@nongnu.org; Wed, 03 Dec 2014 07:10:52 -0500
Message-ID: <1417608638.14168.49.camel@nilsson.home.kraxel.org>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Wed, 03 Dec 2014 13:10:38 +0100
In-Reply-To: <547EDD01.7050608@huawei.com>
References: <1417589746-12176-1-git-send-email-arei.gonglei@huawei.com>
	<20141203093807.GA10160@redhat.com> <547EDD01.7050608@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard
 layout dynamically
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gonglei <arei.gonglei@huawei.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>, "lcapitulino@redhat.com" <lcapitulino@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "Huangpeng (Peter)" <peter.huangpeng@huawei.com>

  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