qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard layou


From: Gonglei
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard layout dynamically
Date: Thu, 4 Dec 2014 10:32:40 +0800
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1

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






reply via email to

[Prev in Thread] Current Thread [Next in Thread]