qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Gonglei <arei.gonglei@huawei.com>
Cc: qemu-trivial@nongnu.org, Wang Xin <wangxinxin.wang@huawei.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-char: add cyrillic key 'numerosign' to Russian keymap
Date: Mon, 16 Feb 2015 11:18:06 +0100	[thread overview]
Message-ID: <1424081886.3722.9.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <54E1AFF2.2070706@huawei.com>

  Hi,

> Both "numbersign" and "numerosign" needed. Although they have the same
> keymap characters, their keysym in vnc_keysym.h are different:
> 
> static const name2keysym_t name2keysym[]={
> ...
>      { "numbersign",           0x023},
> ...
>     +{"numerosign",                    0x06b0},  /* U+2116 NUMERO SIGN */

Not questioning that for the vnc keysym table.

But the russian keymap needs numerosign only, right?
Or does a russian keyboard have *both*?

cheers,
  Gerd

  parent reply	other threads:[~2015-02-16 10:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  4:00 [Qemu-devel] [PATCH 0/2] Fix key 'numerosign' missing in Russian keyboard arei.gonglei
2015-02-16  4:00 ` [Qemu-devel] [PATCH 1/2] qemu-char: add cyrillic characters 'numerosign' to VNC keysyms arei.gonglei
2015-02-16  4:00 ` [Qemu-devel] [PATCH 2/2] qemu-char: add cyrillic key 'numerosign' to Russian keymap arei.gonglei
2015-02-16  8:28   ` Gerd Hoffmann
2015-02-16  8:33     ` Michael Tokarev
2015-02-16  8:53       ` Gonglei
2015-02-16  9:12         ` Michael Tokarev
2015-02-16 10:18         ` Gerd Hoffmann [this message]
2015-02-16 10:27           ` Michael Tokarev
2015-02-16 11:02             ` Gerd Hoffmann
2015-02-25  7:20               ` Gonglei

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=1424081886.3722.9.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=mjt@tls.msk.ru \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=wangxinxin.wang@huawei.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).