Quote:
Originally Posted by sarojane
What I don't understand is what's telling the system (and where it's telling it) what it's supposed to do with these XkbLayout and XkbVariant things. We're just assigning them something here, and it's intuitively clear what those assignments are, and what "layout" and "variant" mean, so how those assignments are going to affect how our system works for us, but the system has no intuition, so somewhere these connections have to be being made. I *really* don't want you to tell me the answer to this specific question.
|
Well, I'll resist! So, ask yourself
1. What does a keyboard driver do?
2. From a programmer's point of view, what do the /usr/share/X11/xkb/symbols/ files look like?
3. Look at /usr/share/X11/xkb/keycodes/evdev and see how it connects to /usr/share/X11/xkb/symbols/us.
I don't know any accessible place that explains keyboards simply (and this is just in the GUI: the console is quite different) — basically I collected little bits over time and wrote my own documentation!
Quote:
I have us driver in twice because I want both variants of it. When I'm typing in Spanish, I want to get accents by typing a quote before a letter. When I'm trying to type in a piece of code, I want a quote to be a quote. (You can type a quote and a space to get a quote, which isn't too bad, but there were other issues like this that I kept tripping over.)
|
If you look at the source for "us international" you can see that "apostrophe" and "quotedbl" are listed — you can get them with AltGr and AltGr-Shift. Alternatively, you can enable a Compose key and use Compose followed by apostrophe and a to get á as I've just done. And a third option would be to modify the standard us layout so that you have entries like
key <TLDE> {[ grave, asciitilde, dead_tilde ]};
One of the things about Linux is that there are so many ways to do everything!