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, 3/4] qemu-char: add support for U-prefixed symbols
Date: Tue, 05 Nov 2013 16:24:31 +0100 [thread overview]
Message-ID: <52790DAF.1090206@suse.com> (raw)
In-Reply-To: <52739068.7090304@msgid.tls.msk.ru>
On 11/01/2013 12:28 PM, Michael Tokarev wrote:
> 01.11.2013 13:59, Michael Tokarev пишет:
>> 16.10.2013 16:40, Jan Krupa wrote:
>>> This patch adds support for Unicode symbols in keymap files. This
>>> feature was already used in some keyboard layouts in QEMU generated
>>> from XKB (e.g. Arabic) but it wasn't implemented in QEMU source code.
>>>
>>> There is no need for check of validity of the hex string after U
>>> character
>>> because strtol returns 0 in case the conversion was unsuccessful.
>>>
>>> Signed-off-by: Jan Krupa <jkrupa@suse.com>
>>>
>>> ---
>>> ui/keymaps.c | 3 +++
>>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/ui/keymaps.c b/ui/keymaps.c
>>> index f373cc5..426a893 100644
>>> --- a/ui/keymaps.c
>>> +++ b/ui/keymaps.c
>>> @@ -33,6 +33,9 @@ static int get_keysym(const name2keysym_t *table,
>>> if (!strcmp(p->name, name))
>>> return p->keysym;
>>> }
>>> + if (strlen(name) == 5 && name[0] == 'U') {
>>> + return (int)strtol(name + 1, NULL, 16);
>>> + }
>>> return 0;
>>> }
>>>
>>
>> I still dislike this. People already complained that the keysyms
>> should be case-insensitive. And there might be many words starting
>> with "u" and of 5 chars long.
>>
>> How about this:
>>
>> Author: Jan Krupa <JKrupa@suse.com>
>> Date: Wed Oct 16 14:40:05 2013 +0200
>>
>> qemu-char: add support for U-prefixed symbols
>>
>> This patch adds support for Unicode symbols in keymap files. This
>> feature was already used in some keyboard layouts in QEMU generated
>> from XKB (e.g. Arabic) but it wasn't implemented in QEMU source
>> code.
>>
>> There is no need for check of validity of the hex string after U
>> character
>> because strtol returns 0 in case the conversion was unsuccessful.
>>
>> Signed-off-by: Jan Krupa <jkrupa@suse.com>
>> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
>>
>> diff --git a/ui/keymaps.c b/ui/keymaps.c
>> index f373cc5..80d658d 100644
>> --- a/ui/keymaps.c
>> +++ b/ui/keymaps.c
>> @@ -33,6 +33,12 @@ static int get_keysym(const name2keysym_t *table,
>> if (!strcmp(p->name, name))
>> return p->keysym;
>> }
>> + if (name[0] == 'U' && strlen(name) == 5) { /* try unicode Uxxxx */
>> + char *end;
>> + int ret = (int)strtoul(name + 1, &end, 16);
>
> Maybe strtol() here as in original.. On my system, both work
> the same anyway :)
Hi Michael,
Thanks for the review! Your change looks good. Agree with adding it this
way.
Jan
next prev parent reply other threads:[~2013-11-05 15:23 UTC|newest]
Thread overview: 13+ 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-10-16 12:40 ` [Qemu-devel] [PATCH v2 2/4] qemu-char: add Czech keymap file Jan Krupa
2013-10-16 12:40 ` [Qemu-devel] [PATCH v2 3/4] qemu-char: add support for U-prefixed symbols 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
2013-11-07 9:10 ` Michael Tokarev
2013-11-01 9:59 ` [Qemu-devel] [v2, 3/4] qemu-char: add support for U-prefixed symbols Michael Tokarev
2013-11-01 11:28 ` Michael Tokarev
2013-11-05 15:24 ` Jan Krupa [this message]
2013-11-01 10:02 ` [Qemu-devel] [v2,2/4] qemu-char: add Czech keymap file Michael Tokarev
2013-11-01 10:01 ` [Qemu-devel] [v2, 1/4] qemu-char: add Czech characters to VNC keysyms 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=52790DAF.1090206@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 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).