From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
Jirka Bohac <jbohac@suse.cz>, lkml <linux-kernel@vger.kernel.org>,
roman@augan.com, hch@nl.linux.org
Subject: Re: [rfc] keytables - the new keycode->keysym mapping
Date: Wed, 9 Feb 2005 17:38:56 +0100 [thread overview]
Message-ID: <20050209163856.GH12100@apps.cwi.nl> (raw)
In-Reply-To: <20050209160345.GA16487@ucw.cz>
On Wed, Feb 09, 2005 at 05:03:45PM +0100, Vojtech Pavlik wrote:
> > It seems very unlikely that you cannot handle Czech with all
> > combinations of 8 keys pressed, and need 9.
>
> A czech keyboard has the letters 'escrzyaie' with accents on the number
> row of keys. With a Shift, they are supposed to produce the original
> numbers, but with a CapsLock, they're supposed to produce the uppercase.
> With a right alt or one of three czech dead keys they should produce
> the !@#$%^&*() symbols.
>
> It's kind of logical, kind of stupid, but anyway it's the national standard.
>
> You can't do that currently. The main problem is that CapsLock is
> hardcoded to work as a Shift on keys and you can't make it work
> differently for normal letter keys and for the upper row of keys.
I think the fallacy in that reasoning is the idea that the key
labeled CapsLock has to be bound to the kernel function named capslock.
Andries
next prev parent reply other threads:[~2005-02-09 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050209132654.GB8343@dwarf.suse.cz>
2005-02-09 15:27 ` [rfc] keytables - the new keycode->keysym mapping Andries Brouwer
2005-02-09 16:03 ` Vojtech Pavlik
2005-02-09 16:38 ` Andries Brouwer [this message]
2005-02-09 16:55 ` Vojtech Pavlik
2005-02-09 19:05 ` Andries Brouwer
2005-02-09 17:19 ` Jirka Bohac
2005-02-09 20:03 ` Andries Brouwer
2005-02-10 12:53 ` Jirka Bohac
[not found] ` <20050216182035.GA7094@dwarf.suse.cz>
2005-02-16 21:49 ` Andries Brouwer
2005-02-17 15:19 ` Jirka Bohac
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=20050209163856.GH12100@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=hch@nl.linux.org \
--cc=jbohac@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=roman@augan.com \
--cc=vojtech@suse.cz \
/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