All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kasai Takanori <kasai.takanori@jp.fujitsu.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] [IOEMU] Fix shift key for graphical vnc display
Date: Fri, 20 Jul 2007 14:40:29 +0100	[thread overview]
Message-ID: <20070720134029.GC10059@redhat.com> (raw)
In-Reply-To: <169b01c7cab2$de557380$dab2220a@VF03007L>

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  -=| 

  reply	other threads:[~2007-07-20 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20  9:45 [PATCH] [IOEMU] Fix shift key for graphical vnc display Kasai Takanori
2007-07-20 13:40 ` Daniel P. Berrange [this message]
2007-07-23  2:59   ` [PATCH] [IOEMU] Fix shift key for graphical vncdisplay Kasai Takanori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070720134029.GC10059@redhat.com \
    --to=berrange@redhat.com \
    --cc=kasai.takanori@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.