Re: [patch 0/2] vdagent KEYVAL extension

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

 




----- Original Message -----
> 
> 
> ----- Original Message -----
> > > Yes, although I think we should be able to send arbitrary utf8 input in
> > > the
> > > protocol. If I read your proposal right, you are sending UCS-4 codes, no
> > > utf8?
> > > 
> > > I think you should use gdk_keyval_to_unicode() then g_ucs4_to_utf8() for
> > > key
> > > input and efficiency (in your spice-gtk patch).
> > 
> > Unfortunately, the unicode people forgot to add values for function keys
> > and
> > other special
> > keys! That is why I use the X11 keysmys - they can also represent all keys
> > on
> > the keyboard.
> > AFAIK VNC protocol also use that.
> 
> Keys that don't have utf8 equivalent should be sent with the current input, I
> don't see a benefit changing that.
> 
> Having a utf8 input is mainly useful for utf8 input from client (input
> method, browser) and to bypass guest keymaps.

I realize you may just want to receive client keysyms, and not the XT scancode (because you don't have any keymap and talk directly to a process)... In this case, your patch would make sense, and open the door to higher-level inputs ;)

_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]