All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel@nongnu.org, "Oleg L. Sadov" <sadov@linux-ink.ru>
Subject: Re: Testing of russian keymap (was Re: [Qemu-devel] [PATCH] fix '/' and	'|' on russian keymap)
Date: Thu, 07 Oct 2010 08:38:32 +0400	[thread overview]
Message-ID: <4CAD4EC8.5070402@msgid.tls.msk.ru> (raw)
In-Reply-To: <20101006195607.GB20664@blackpad.lan.raisama.net>

06.10.2010 23:56, Eduardo Habkost wrote:
> 
> Anybody using a russian keyboard layout who can test this change and
> confirm it works as expected?

I can perform such a testing - in theory.  But in practice, I was never
able to figure out this -k $lang stuff, -- neither in qemu nor in other
apps like rdesktop and the like.

What I usually do is to explicitly set en-us keyboard for applications
that are "too smart" and tries to guess "right" keyboard from env.
variables such as $LANG.

The reason is that after specifying "ru" keyboard, I can't use latin
chars anymore, and can type only using cyrillic.  Since cyrillic
layout does not have any latin char, imagine how to type, say, a
path name (even "C:" drive in windows).

All modern OSes nowadays have a way to switch between keyboard layouts
dynamically - this is done internally in the operating system.  So,
basically, I've no idea what this -k $foo stuff is used for to start
with ;)

Care to explain please?  Oleg?  :)

Thanks!

/mjt

  reply	other threads:[~2010-10-07  4:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 18:14 [Qemu-devel] [PATCH] fix '/' and '|' on russian keymap Eduardo Habkost
2010-10-06 19:56 ` Testing of russian keymap (was Re: [Qemu-devel] [PATCH] fix '/' and '|' on russian keymap) Eduardo Habkost
2010-10-07  4:38   ` Michael Tokarev [this message]
2010-10-18 17:30     ` Oleg Sadov
2010-10-18 18:59       ` Anthony Liguori
2010-10-19  9:32         ` Daniel P. Berrange
2010-10-19 14:16           ` Oleg Sadov
2010-10-07  4:47   ` 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=4CAD4EC8.5070402@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=sadov@linux-ink.ru \
    /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.