![]() ![]() They had separate upstreams and separate histories even maps which happened to have the same name in both schemes were not necessarily the same. Prior to Fedora 20, we had two entirely separate sets of keyboard layout maps: one for kbd, one for xkb. But for the purposes of this, the key point is that it uses layout maps of a different format, stored in a different location, and in the xkb world, switching between layouts is normal and expected behaviour. That's it.)Īt the X level, keyboard input is handled by xkb, about the complexity of which I have written before. (The way 'configuration' works for kbd is really bone simple: somewhere during init there's a very trivial function which reads a config file, gets a layout name from it, and runs 'loadkeys (layout)'. There is no standard daemon or anything for switching between different layout map files, in this system: it's expected you pretty much load a single layout file and stick with it. The 'loadkeys' utility loads keyboard layout maps of a given format from a given location. Console keyboard input basically happens in the kernel, with some very simple userspace utilities available to configure things in the 'kbd' package. In Linux, keyboard input at the console and X levels is actually handled differently. And write a (Fairly) Short History of Fedora Keyboard Input, while I'm at it. I spent some time this week trying to help clean up the behaviour of Fedora 20 in regard to keyboard layouts, so I thought I'd write it up here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |