From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: [PATCH] [IOEMU] Fix shift key for graphical vnc display Date: Fri, 20 Jul 2007 14:40:29 +0100 Message-ID: <20070720134029.GC10059@redhat.com> References: <169b01c7cab2$de557380$dab2220a@VF03007L> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <169b01c7cab2$de557380$dab2220a@VF03007L> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kasai Takanori Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Jul 20, 2007 at 06:45:35PM +0900, Kasai Takanori wrote: > Hi All, > > There is a problem in the input of the key in the VNC connection on the HVM > domain. > When client's keyboard is not the same as the kind of the keyboard of > qemu-dm > and GuestOS, it is not possible to input it correctly. > > VNC client qemu-dm & GuestOS > --------------+----------------------- > ja en-us ==> NG > en-us en-us ==> OK I thought the idea of the 'keymap' entry in the vfb config was that you would setup 'qemu-dm' & the GuestOS to be 'ja' too. Trying to make the 'ja' -> 'en-us' conversion work doesn't sound like the kind of thing that would ever work in the general case. Does the 'ja' -> 'ja' case currently work ? Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|