From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I7CSC-0001AJ-Js for qemu-devel@nongnu.org; Sat, 07 Jul 2007 11:44:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I7CSA-000196-W5 for qemu-devel@nongnu.org; Sat, 07 Jul 2007 11:44:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I7CSA-000193-QZ for qemu-devel@nongnu.org; Sat, 07 Jul 2007 11:44:10 -0400 Received: from wa-out-1112.google.com ([209.85.146.179]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I7CSA-0005Wp-8I for qemu-devel@nongnu.org; Sat, 07 Jul 2007 11:44:10 -0400 Received: by wa-out-1112.google.com with SMTP id k22so715542waf for ; Sat, 07 Jul 2007 08:44:08 -0700 (PDT) Message-ID: <83a4d4ca0707070844s64138e26hc5aa944c02847791@mail.gmail.com> Date: Sat, 7 Jul 2007 17:44:08 +0200 From: "Eduardo Felipe" Subject: Re: [Qemu-devel] vnc with german keymap In-Reply-To: <20070706170805.GA7833@saturn.kn-bremen.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_171882_3825779.1183823048671" References: <20070704002405.GA26287@saturn.kn-bremen.de> <83a4d4ca0707040109o242dc1f9s7e5c8c046baf2f6a@mail.gmail.com> <200707041948.l64JmFFv011243@saturn.kn-bremen.de> <83a4d4ca0707050142m3cd2fb93w30c3dbe61d33c610@mail.gmail.com> <20070706170805.GA7833@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: Juergen Lock Cc: qemu-devel ------=_Part_171882_3825779.1183823048671 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 2007/7/6, Juergen Lock : > > On Thu, Jul 05, 2007 at 10:42:03AM +0200, Eduardo Felipe wrote: > > > Your VNC client probably sends deadkey messages... or maybe I have a > > complicated way to handle simple things :) > > Yup, I tested with tightvnc-1.3.8. I've tried tightvnc and it does send deadkey messages. By contrast, RealVNC is an example of client that sends extended Latin-1 (or similar) characters. (You might want to explain this fact on the list tho, it may have been > the reason your patch wasn't committed...) > > Bye, > Juergen > Agreed, cc'ing. I just forgot to "Reply-to-all" last time... Regards, Edu ------=_Part_171882_3825779.1183823048671 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2007/7/6, Juergen Lock <nox@jelal.kn-bremen.de>:
On Thu, Jul 05, 2007 at 10:42:03AM +0200, Eduardo Felipe wrote:

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

Yup, I tested with tightvnc-1.3.8.

I've tried tightvnc and it does send deadkey messages. By contrast, RealVNC is an example of client that sends extended Latin-1 (or similar) characters.

(You might want to explain this fact on the list tho, it may have been
the reason your patch wasn't committed...)

Bye,
        Juergen

Agreed, cc'ing. I just forgot to "Reply-to-all" last time...

Regards,
Edu
------=_Part_171882_3825779.1183823048671--