From: Michael Tokarev <mjt@tls.msk.ru>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "R. Lemos" <rslemos@gmail.com>,
772422@bugs.debian.org, qemu-devel <qemu-devel@nongnu.org>,
Joao Luis Meloni Assirati <jlma@nonada.if.usp.br>
Subject: Re: [Qemu-devel] ABNT2 keys again
Date: Fri, 22 May 2015 16:10:31 +0300 [thread overview]
Message-ID: <555F2AC7.80807@msgid.tls.msk.ru> (raw)
In-Reply-To: <1432288894.12533.43.camel@nilsson.home.kraxel.org>
22.05.2015 13:01, Gerd Hoffmann wrote:
> On Mi, 2015-05-20 at 14:44 +0300, Michael Tokarev wrote:
>> A (friendly) ping? :)
>>
>>> The solution appears to be trivial (see also some background
>>> at http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/ ),
>>> but the problem is definitely still here.
>>>
>>> Maybe it's a time to address this finally? :)
>>>
>>> I don't pretend to understand any significant bit of input
>>> handling, so am asking people who are more knowlegeable in
>>> this area to take a look ;)
>
> Anyone having such a keyboard and willing to run some tests?
Adding Cc's. This has been reported to debian too,
http://bugs.debian.org/772422 (also in Cc).
Thanks,
/mjt
next prev parent reply other threads:[~2015-05-22 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 5:01 [Qemu-devel] ABNT2 keys again Michael Tokarev
2015-05-20 11:44 ` Michael Tokarev
2015-05-22 10:01 ` Gerd Hoffmann
2015-05-22 13:10 ` Michael Tokarev [this message]
2015-05-22 13:20 ` Gerd Hoffmann
2015-05-22 13:39 ` Michael Tokarev
2015-05-22 16:10 ` Joao Luis Meloni Assirati
2015-05-26 7:58 ` Gerd Hoffmann
2015-05-26 20:51 ` Joao Luis Meloni Assirati
2015-05-27 14:11 ` Gerd Hoffmann
2015-05-26 14:01 ` Gerd Hoffmann
2015-05-26 15:52 ` R. Lemos
2015-05-26 21:24 ` Joao Luis Meloni Assirati
2015-05-27 14:18 ` Gerd Hoffmann
2015-05-22 15:03 ` Joao Luis Meloni Assirati
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=555F2AC7.80807@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=772422@bugs.debian.org \
--cc=jlma@nonada.if.usp.br \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rslemos@gmail.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.