English with accents.
kernel 2.6.21.5, slackware 12.0
Hi: I once had a Window$ OS that came with what they called "English with accents" (EA). I am used to the US keyboard (kb) layout. The EA feature, had the US kb layout. But there was a difference: you could press Meta+'`' (ascii 0x60) and the cursor did not advance. Now you wrote a letter. And the letter got accentuated. So this is a question not of kb layout but of kb behavior: some keys, in combination with the Alt key, if Alt is the Meta key, do not make the cursor move. Any hint? |
Read up on how to map a key on your keyboard to the Compose key. That should be pretty much what you're after. The neat thing about it is that you can do way more than just accent vowels with it: ®©ÆŒåÅø¢£, etc. :D
Here is an excellent list of Compose sequences you can experiment with. |
MTK had a blog on the compose keys, perhaps that'll be helpful here: http://www.linuxquestions.org/questi...key-in-x-2885/
|
This is unbelievable. It works to perfection. Hail MTK. And Anisha Kaul too. Unfortunately, I sometimes compose my letters with vim, working in a virtual terminal (VT). Can this be done in a VT?
|
I have a US keyboard. I've set it to US-International.
I can now type using it in French, Spanish, and some eastern European languages: áéíóúàèìòùäëïöü ¿ ñ ç ćś etc ... use this: Code:
system-config-keyboard type 'space and you'll get ' |
Hi:
Thanks for the post. 'system-config-keyboard' at a console (VT) gets command not found. Then I did this: I booted with the slackware instalation disc and first thing I am asked for is to choose a keyboard map. There were about a hundred of them. I chose querty/us-acentos.map. Then it said: "OK, the <don't remember what> is loaded now. Type any key you want to test. Then type 1 to accept and go on". When I typed "'" or "`" the keyboard stoped to echo. I had to use then backspace. Finally I type '1' on a line by itself and finally exited the setup (I entered typing 'setup'). However, in a console, it's the same as before: no accents (acentos in Spanish means accents). Well, perhaps I should have going on with the rest of the steps in 'setup'. I don't know. I'll try again. Perhaps for this 'setup' thing, I must use a Spanish or French keyboard. But that would not do for me, as some keys in those keyboards are arranged in a completely different way. Regards. |
As you've seen, the console and Xorg manage their keyboards quite differently. Have a look in
/lib/kbd/keymaps/i386/qwerty/us-acentos.map.gz and you can see what it does and (if necessary) alter it. The grave accent key defaults to a dead grave, so it won't display anything if you press it. |
# 5 : Just for information :
Quote:
|
This file I have it in /usr/share/kbd/keymaps/i386/qwerty/us-acentos.map.gz
I gzip -dv it and part of it is this: Code:
compose '`' 'A' to 'À' |
I downloaded system-config-keyboard-1.3.0.tar.gz. Then, I made [code]
$ make $ make install make: intltool-merge: Command not found make: *** [system-config-keyboard.desktop] Error 127 $ [code] What's wrong? |
All that system-config-keyboard does is edit a configuration file to insert the name of your default keyboard: you could do that yourself. And since it's a Red Hat tool, it may not even find the file on Slackware. As you've seen, Red Hat and Slackware put the console keyboard maps in completely different places!
|
Quote:
|
Quote:
Quote:
|
No. The only paths where the element /sysconfig/ appears are
/usr/lib/python23.5 /usr/doc/python-2.5.1 I did 'locate keyboard'. This output nearly 350 lines. From among them, I list the following: /usr/lib/qt-3.3.8/doc/html/qkeyboard_qws-h.html /usr/lib/qt-3.3.8/doc/html/qwskeyboardhandler.html /usr/lib/qt-3.3.8/doc/html/qwskeyboardhandler-members.html /usr/man/man3/keyboard_init_return_fd.3.gz /usr/man/man3/keyboard_init.3.gz /usr/man/man3/keyboard_getstate.3.gz /usr/man/man3/keyboard_seteventhandler.3.gz /usr/man/man3/qwskeyboardhandler.3qt.gz /usr/man/man3/keyboard_update.3.gz /usr/man/man3/keyboard_keypressed.3.gz /usr/man/man3/keyboard_clearstate.3.gz /usr/man/man3/keyboard_setdefaulteventhandler.3.gz /usr/man/man3/keyboard_close.3.gz /usr/man/man3/keyboard_translatekeys.3.gz /usr/man/man3/keyboard_waitforupdate.3.gz /usr/doc/xsl-stylesheets-1.72.0/slides/keyboard.nav.html /usr/doc/HTML/en/kcontrol/keyboard /usr/doc/HTML/en/kcontrol/keyboard/index.cache.bz2 /usr/doc/HTML/en/kcontrol/keyboard/index.docbook /usr/doc/HTML/en/kcontrol/keyboard/common /usr/doc/HTML/en/ktouch/keyboard_options.png /usr/doc/SDL-1.2.11/html/guideinputkeyboard.html /usr/doc/SDL-1.2.11/html/sdlkeyboardevent.html /usr/doc/gqview-2.1.5/html/11_2_keyboard_shortcuts.html /usr/doc/lilo-22.8/README.nokeyboard /usr/share/system-config-keyboard/system-config-keyboard.py There are a lot under /usr/src/linux-2.6.21.5/drivers/input/keyboard/ If you can find some suggestive name here, please tell me. Otherwise, let us be it. Regards. |
I was looking for certain command, because I had seen, in LQ, mentioned certain command very similar to hexdump. So I did find /usr/bin -name "*dump*". And among the many names listed by 'find', I set my eyes in a dumpkeys name.
It happens that there are the following commands in Slackware 12.0: loadkeys, dumpkeys, showkey and keymaps. Using these commands is the answer to issue being ventilated here. But I must study the manuals. Regards. |
All times are GMT -5. The time now is 08:05 AM. |