From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I6NtX-0002jc-M9 for qemu-devel@nongnu.org; Thu, 05 Jul 2007 05:45:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I6NtW-0002jH-3x for qemu-devel@nongnu.org; Thu, 05 Jul 2007 05:45:03 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6NtW-0002jE-1O for qemu-devel@nongnu.org; Thu, 05 Jul 2007 05:45:02 -0400 Received: from wa-out-1112.google.com ([209.85.146.176]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I6NtV-0000Z3-AX for qemu-devel@nongnu.org; Thu, 05 Jul 2007 05:45:01 -0400 Received: by wa-out-1112.google.com with SMTP id k22so3606950waf for ; Thu, 05 Jul 2007 02:44:59 -0700 (PDT) Message-ID: <83a4d4ca0707050244p2e9ffc98j867df639f793a770@mail.gmail.com> Date: Thu, 5 Jul 2007 11:44:58 +0200 From: "Eduardo Felipe" Subject: Re: [Qemu-devel] vnc with german keymap In-Reply-To: <200707041948.l64JmFFv011243@saturn.kn-bremen.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_141505_10456622.1183628698404" References: <20070704002405.GA26287@saturn.kn-bremen.de> <83a4d4ca0707040109o242dc1f9s7e5c8c046baf2f6a@mail.gmail.com> <200707041948.l64JmFFv011243@saturn.kn-bremen.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_141505_10456622.1183628698404 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 2007/7/4, Juergen Lock : > > > Ah, thanx, I didnt see that one! :) > > I have a qeuestion tho: does this patch do deadkey handling on the host? Yes. IIRC I needed that because some VNC clients I tested didn't send dead keys to the server. They just waited for a full character to be available i= n its buffer to send the KeyEvent message, as they assume the server will kno= w how to represent it. That is, if I press =B4 and o in some VNC clients, onl= y an =F3 (0x00f3) message is sent after pressing the last key, not the 0xfe51= / 0x006f combination. The server (qemu) has to know how to build the characte= r for its guest. Because I didn't have to do anything like that for the de patch, the > guest could do that itself just fine. (tested with a linux livecd > guest with (under X) and without deadkeys (console).) > > Your VNC client probably sends deadkey messages... or maybe I have a complicated way to handle simple things :) Regards, Edu ------=_Part_141505_10456622.1183628698404 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
2007/7/4, Juergen Lo= ck <nox@jelal.kn-bremen.de>:

Ah, thanx, I didnt see that one! :)

I have a = qeuestion tho: does this patch do deadkey handling on the host?

Yes. IIRC I needed that because some VNC clients I tested didn't send dead keys to the server. They just waited for a full character to be available in its buffer to send the KeyEvent message, as they assume the server will know how to represent it. That is, if I press =B4 and o in some VNC clients, only an =F3 (0x00f3) message is sent after pressing the last key, not the 0xfe51 / 0x006f combination. The server (qemu) has to know how to build the character for its guest.

Because I didn't have to do anything like that for the de patch, theguest could do that itself just fine.  (tested with a linux live= cd
guest with (under X) and without deadkeys (console).)


Your VNC client probably sends deadkey messages... or maybe I have a co= mplicated way to handle simple things :)

Regards,
Edu ------=_Part_141505_10456622.1183628698404--