From: Stian Sletner <stian@sletner.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] Dead keys
Date: Tue, 1 May 2001 21:29:55 +0200 [thread overview]
Message-ID: <20010501212955.B17376@sletner.com> (raw)
In-Reply-To: <UTC200105011920.VAA57933.aeb@vlet.cwi.nl>
In-Reply-To: <UTC200105011920.VAA57933.aeb@vlet.cwi.nl>; from Andries.Brouwer@cwi.nl on Tue, May 01, 2001 at 09:20:12PM +0200
* At 2001-05-01T21:20+0200, Andries.Brouwer@cwi.nl wrote:
:
| I think the main reason why it shouldn't be applied is that it changes
| something. This keyboard stuff is unbelievably complicated. Many people
| and distributions have wrestled with it and have got it working for them.
| When you change stuff, you force people to start worrying about this again.
|
| [In other words, a global rewrite may be allowed, but non-compatible changes
| in a few details only is really a bad idea.]
Won't comment on this argument, it might outweigh my point (but that's
not for me to say).
| But there are other reasons why your patch is a bad idea. Everybody has
| a double quote in his keymap, so using that to create umlauts is easy.
| Only few people have a diaeresis in their keymap, so requiring a diaeresis
| makes life more difficult for most people.
It doesn't require anyone to use the ISO characters. The defkeymap.map
still contains compose rules for the ASCII sequences.
| (In other words, composing ASCII to make ISO 8859-1 is better than composing
| ISO 8859-1 to make ISO 8859-1.)
This is just a matter of adding compose rules. The issue here is that
the dead keys themselves are producing the wrong characters.
| Finally, you have loadkeys. If you change your private keymap
| you achieve what you desire for yourself without disturbing others.
No, this doesn't seem to be the case, unless I've missed something
important. Because the dead_* are wrong, and I can't change them with a
keymap, afaik? If I'm wrong, shoot me, then the patch is pointless.
--
Stian Sletner
next prev parent reply other threads:[~2001-05-01 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 19:20 [PATCH] Dead keys Andries.Brouwer
2001-05-01 19:29 ` Stian Sletner [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-01 23:12 Andries.Brouwer
2001-05-01 23:39 ` Stian Sletner
2001-05-01 18:04 Stian Sletner
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=20010501212955.B17376@sletner.com \
--to=stian@sletner.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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