Dead keys
From [email protected] Tue May 1 20:05:26 2001
Normally, you wouldn't notice this too much, since the compose rules are set up in such a way that you can use the dead keys to compose what you would expect, anyway. However, if you were to press a dead key and then space, or some un-composable key (to get the dead key character by itself), you would get the wrong character. Instead of '�' (ISO 8859-1 decimal 168: DIAERESIS), you would get '"' (ASCII decimal 34); instead of '�' (ISO 8859-1 decimal 180: ACUTE ACCENT), you would get '\'' (ASCII decimal 39); and instead of '�' (ISO 8859-1 decimal 184: CEDILLA), you would get ',' (ASCII decimal 44).
I took the liberty of creating a patch that changes this in keyboard.c, and also adds compose rules to defkeymap.map so they can be used properly. If there is some reason why this shouldn't be applied, I'd like to know what, since this makes my console life easier. :)
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.]
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.
(In other words, composing ASCII to make ISO 8859-1 is better than composing ISO 8859-1 to make ISO 8859-1.)
Finally, you have loadkeys. If you change your private keymap you achieve what you desire for yourself without disturbing others.
Andries
* At 2001-05-01T21:20+0200, [email protected] 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.
Signature · 1 line
Stian Sletner