All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Xen-devel@lists.xensource.com,
	Junko Ichino <ichino.junko@jp.fujitsu.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [RFC] keymap support for PVFB
Date: Fri, 12 Jan 2007 12:16:53 +0000	[thread overview]
Message-ID: <20070112121652.GA5566@redhat.com> (raw)
In-Reply-To: <45A74399.6080401@suse.de>

On Fri, Jan 12, 2007 at 09:15:21AM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> >> I've tried to tackle the same issue by hacking the vnc client side to
> >> send us keysyms no matter what the local keyboard mapping is.  So I can
> >> have any keyboard map loaded on the host, qemu-dm/vncfb sees us keysyms
> >> nevertheless and passes the correct scancodes to the guest OS.
> > 
> > You mean scan codes, don't you?  Key symbols are the XK_a and so
> > forth.
> 
> No, keysyms.  This is what the vnc protocol uses, so there is no way
> around that, unfortunaly.  It takes the X11 keycodes and translates
> these to us keymap keysyms using a buildin table, then sends them.  So
> for the server side (from vnc protocol view, i.e. qemu-dm or vnc-fb) it
> looks like a vnc client with us keyboard.
> 
> > Passing scan codes in addition to key symbols makes sense.
> 
> Does the vnc protocol allow that?  I don't think so :-(

No, but there's no reason we couldn't come up with an extension. Anthony
has already done similar to allow passing of relative mouse co-ords instead
of absolute co-ords. Extensions are opt-in, so unless the client has support
they'd carry on with normal keysyms, but a client that understood the new
extension could switch to scan codes. The important thing is talking to
upstream VNC mailing lists about any proposed extension to get buy-in so
some of the popular clients implement it. As far as i'm concerned, I'm more
than happy to extend the virt-manager  VNC client if it could enable better
internationalized keyboard handling.

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

  parent reply	other threads:[~2007-01-12 12:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28  4:11 [RFC] keymap support for PVFB Junko Ichino
2006-12-28 16:02 ` Ewan Mellor
2007-01-09  0:56   ` Kasai Takanori
2007-01-09  1:07   ` Junko Ichino
2007-01-10 20:18 ` Markus Armbruster
2007-01-11  9:09   ` Gerd Hoffmann
2007-01-11 17:53     ` Markus Armbruster
2007-01-12  8:15       ` Gerd Hoffmann
2007-01-12 10:48         ` Markus Armbruster
2007-01-12 11:02           ` Gerd Hoffmann
2007-01-12 12:16         ` Daniel P. Berrange [this message]
2007-01-11 14:09   ` Junko Ichino
2007-01-11 17:54     ` Markus Armbruster
2007-01-17  6:07       ` Junko Ichino
2007-01-17  7:48         ` Markus Armbruster
2007-01-17  9:39           ` Junko Ichino
2007-01-17 10:21             ` Markus Armbruster
2007-01-17 11:39               ` Junko Ichino
2007-01-17 12:46                 ` Kasai Takanori
2007-01-17 13:25                 ` Markus Armbruster
2007-01-18 12:17                   ` Junko Ichino
2007-01-18 15:01                     ` Markus Armbruster
  -- strict thread matches above, loose matches on Subject: below --
2007-01-12 12:35 Bruce Rogers
2007-01-12 13:32 ` Daniel P. Berrange

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=20070112121652.GA5566@redhat.com \
    --to=berrange@redhat.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=armbru@redhat.com \
    --cc=ichino.junko@jp.fujitsu.com \
    --cc=kraxel@suse.de \
    /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.