From: Jan Krupa <JKrupa@suse.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [v2, 4/4] qemu-char: add missing characters used in keymaps
Date: Tue, 05 Nov 2013 16:26:13 +0100 [thread overview]
Message-ID: <52790E15.1000006@suse.com> (raw)
In-Reply-To: <52737BBA.4060109@msgid.tls.msk.ru>
On 11/01/2013 11:00 AM, Michael Tokarev wrote:
> 16.10.2013 16:40, Jan Krupa wrote:
>> This patch adds all missing characters used in regional keymap
>> files which already exist in QEMU. I checked for the missing
>> characters by going through all of the keymaps and matching that
>> with records in vnc_keysym.h. If the key wasn't found I looked
>> it up in libxkbcommon library [1]. If I understood it correctly
>> this is also the same place where most of the keymaps were
>> exported from according to the comment on the first line in those
>> files. I was able to find all symbols except "quotebl" used
>> in Netherland keymap.
>>
>> I tested this update with Czech keyboard by myself. I also asked
>> Matej Serc to test Slovenian keyboard layout - he reported problems
>> with it few days ago on this mailing list. Both layouts seems
>> to work fine. I wasn't able to test the remaining layouts but
>> since this change doesn't modify any existing symbols, just adds
>> new ones, I don't expect any sideeffects.
>
> Yes, this patch, while large, is trivial and without any side effects.
>
> Except of one question. Where we add these entries? Should we maybe
> sort the table somehow, or introduce some more groups of chars?
>
> (I'm fine with applying this to qemu-trivial as-is).
I agree with sorting those entries to groups. But I think this is not a
straightforward task without completely rewriting the current groups
which seems to be a bit chaotic. Maybe what would be a good inspiration
is this libxkbcommon header file (which was probably used as a base data
for the current vnc_keysym.h, too):
http://cgit.freedesktop.org/xorg/lib/libxkbcommon/tree/xkbcommon/xkbcommon-keysyms.h
We can convert it into vnc_keysym.h retaining the groups used in
libxkbcommon, there. If you agree I can prepare patch for review.
Jan
next prev parent reply other threads:[~2013-11-05 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 12:40 [Qemu-devel] [PATCH v2 0/4] qemu-char: keymap changes for Czech and Unicode support Jan Krupa
2013-10-16 12:40 ` [Qemu-devel] [PATCH v2 1/4] qemu-char: add Czech characters to VNC keysyms Jan Krupa
2013-11-01 10:01 ` [Qemu-trivial] [v2, " Michael Tokarev
2013-11-01 10:01 ` [Qemu-devel] " Michael Tokarev
2013-10-16 12:40 ` [Qemu-devel] [PATCH v2 2/4] qemu-char: add Czech keymap file Jan Krupa
2013-11-01 10:02 ` [Qemu-trivial] [v2,2/4] " Michael Tokarev
2013-11-01 10:02 ` [Qemu-devel] " Michael Tokarev
2013-10-16 12:40 ` [Qemu-devel] [PATCH v2 3/4] qemu-char: add support for U-prefixed symbols Jan Krupa
2013-11-01 9:59 ` [Qemu-devel] [v2, " Michael Tokarev
2013-11-01 11:28 ` Michael Tokarev
2013-11-05 15:24 ` Jan Krupa
2013-10-16 12:40 ` [Qemu-devel] [PATCH v2 4/4] qemu-char: add missing characters used in keymaps Jan Krupa
2013-11-01 10:00 ` [Qemu-devel] [v2, " Michael Tokarev
2013-11-05 15:26 ` Jan Krupa [this message]
2013-11-07 9:10 ` Michael Tokarev
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=52790E15.1000006@suse.com \
--to=jkrupa@suse.com \
--cc=anthony@codemonkey.ws \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/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.