From: "Joao Luis Meloni Assirati" <jlma@nonada.if.usp.br>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: 772422@bugs.debian.org, Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
"R. Lemos" <rslemos@gmail.com>,
Joao Luis Meloni Assirati <jlma@nonada.if.usp.br>
Subject: Re: [Qemu-devel] ABNT2 keys again
Date: Tue, 26 May 2015 17:51:23 -0300 [thread overview]
Message-ID: <fb4e28f6ffdd3d0180bbdd473ba6fe15.squirrel@nonada.if.usp.br> (raw)
In-Reply-To: <1432627120.28482.5.camel@nilsson.home.kraxel.org>
Hello,
>> 12:44:02.389552: EV_MSC MSC_SCAN 458887 <== Here, / was pressed
>> 12:44:02.389552: EV_KEY KEY_RO (0x59) pressed
>
> 'RO'. Hmm, not very descriptive. Any idea what this could stand for?
RO stands for Romaji, which is japanese with roman letters (transliteration).
>
>> 12:44:04.253486: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was
>> pressed
>> 12:44:04.253486: EV_KEY KEY_KPCOMMA (0x79) pressed
>
> Ok. Is there a key with ',' too in your numpad?
Yes, there is a separated ',' in the numpad, and when I press it I get
17:48:47.878881: EV_MSC MSC_SCAN 458851
17:48:47.878881: EV_KEY KEY_KPDOT (0x53) pressed
17:48:47.878881: EV_SYN code=0 value=0
^[[3~17:48:47.966876: EV_MSC MSC_SCAN 458851
17:48:47.966876: EV_KEY KEY_KPDOT (0x53) released
17:48:47.966876: EV_SYN code=0 value=0
Apparently the codes are exchanged in ABNT2 numpad.
Thanks,
Joao Luis.
next prev parent reply other threads:[~2015-05-26 20:51 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
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 [this message]
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=fb4e28f6ffdd3d0180bbdd473ba6fe15.squirrel@nonada.if.usp.br \
--to=jlma@nonada.if.usp.br \
--cc=772422@bugs.debian.org \
--cc=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).