Non-US keyboard layout in Xorg

Hello,
I have a Belgian keyboard layout and had some troubles with the Alt-Gr key.
We combine this key with other keys to generate special symbols like the Euro sign or the @ character for example.
I found several solutions on several websites but they didn't seem to work for me.
I now added the following line in my /etc/X11/xinit/xinitrc and now it's working:
setxkbmap be
Perhaps it's not a bad idea to add this setxkbmap command to the Xorg package, since I noticed I was not the only
one who was struggling with this problem.
Regards,
Solley

My XORG look like that:
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us,lt"
Option "XkbOptions" "grp:alt_shift_toggle"
Driver "kbd"
EndSection

Similar Messages

Non-english keyboard layouts work in some programs, not others

In some programs, I can set a non-English keyboard layout and have the appropriate behavior when it comes to diacritics - in, say, the brazilian layout, hitting { then a will give me a á, and so on. It works perfectly fine in Firefox and xchat, for instance. But in other programs, opera and openoffice to name two I've tried, this fails. I either get a garbage character when I hit the first diacritic key or I just get the diacritic by itself and then the accentless vowel: ´a.
Completely non-English characters still work fine; I can get ç in the Brazilian layout and ñ in Latin American and the Georgian one works fine too, since Georgian doesn't have diacritics I presume. It's just diacritics that don't work.
I first noticed this problem after I installed SCIM, so I assume it has something to do with the SCIM installation, but I don't know what I did in the process of installing it that would've messed things up.

thayer wrote:Your best bet would be to post your problem to the dwm mailing list:
[email protected]
Will do...
Thanks!

[LR2 - SOLUTION] Using Lightroom in englsih with a non-english keyboard layout

Hi, Many of us, non native english speaking LR users, are using LT in english on a system having a non-US keyboard layout. The conseqeunce of this is that we can't reach a lot of keyboard shortcuts because LR doesn't offer any interface for configuring them. However, there's a workaround. I'll explain here what I did for the french language but you can apply this to your own language. For the non english languages, the keyboard shortcuts are defined in C:\Program Files\Adobe\Adobe Photoshop Lightroom 2\Resources\<language>\TranslatedStrings.txt. If you are using LR in english, this file is not used and there's no similar file in C:\Program Files\Adobe\Adobe Photoshop Lightroom 2\Resources\en. But you can create one containing only the shortcuts that you need. I have created a new TranslatedStrings.txt file containing only the keyboard shortcuts defined for the french version. I did this by copying only the lines containing the following sequences: ....Key=... ....KeyShifted=... ...AgPanel/LeftPanelShortcut... ...AgPanel/RightPanelShortcut... ...MenuShortcut/DecreaseRating= ...MenuShortcut/IncreaseRating= (french users can find this file here: http://www.mainsoft.fr/Files/LR/TranslatedStrings.txt . Copy this file to "C:\Program Files\Adobe\Adobe Photoshop Lightroom 2\Resources\en" and relaunch Lightroom. Now you have the same keyboard shortcuts as when using LR in french. Interestingly enough, if you hit ctrl + < , the LR keyboard shortcut panel is displayed and it shows your new shortcuts. Again, you can do the same for your own language by copying the specified strings from the relevant folder. Hope this helps. -- Patrick Philippot MainSoft Consulting Services www.mainsoft.fr

Yes… I would at a minimum contact Apple sales or AppleCare regarding this. You have two options though. You can ask for a new one, given they can't simply swap out a keybaord you need to exchange the whole thing.
Otherwise, you can use it as a bargaining chip and say ask for a free external International English keyboard and a discount on your next Apple Store purchase… for instance.
Regardless, be polite yet firm with them as you did not get what you ordered.

NCS and non US keyboard layout - Guest - Email ID and @

Problem:
The problem is that we cannot email the Guest Account Details to the guest, because the popup where we fill in the email of the guest - Email ID - Does not recognise the @ when using non US Keyboard layout.
When i use my local keyboard layout (Danish) and press AltGr+2 (this is the keyboard "shortcut" for @) it writes nothing.
When i switch to US keyboard layout and press Shift+2 it writes @ fine.
Version:
Tried this in both 1.0 and I just upgraded to 1.1 and it is still the same.
Does anyone know of a open BugID that addresses the following problem on the NCS Lobby Ambasador page ?

Thomas,
Have you tried it from different machines and different OSes and confirmed that the common denominator is NCS and not your specific KB/OS setup?
Justin
Sent from Cisco Technical Support iPhone App

[SOLVED] Can't change keyboard Layout on Xorg 1.8

Hi all
I'm trying to configure the Input Hot-plugging on Xorg 1.8 but the keyboard layout is still on US keyboard and I need to change it.
I use some of the configurations of some people of the forum but it still on US, now my 10-evdev-conf file is like this:
Section "InputClass"
Identifier "Keyboards Defaults"
Driver "evdev"
Option "XkbLayout" "latam"
Option "XkbModel" "microsoft"
MatchIsKeyboard "on"
EndSection
If there are a similar topic, Can you put the link?
Thanks
Last edited by MiloCB04 (2010-06-25 04:22:30)

Sorry, but i found the problem, I saved 10-evdev.conf as 10-evdev-conf, and here is my code
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbLayout" "be"
EndSection
Section "InputClass"
Identifier "mouse-all" ## to use a PS/2 mouse :P
MatchIsPointer "on"
Driver "evdev"
EndSection
so I hope that someone can use this solve

Screen locked with non-English keyboard layout selected

Hello,
I use two keyboard character sets for keyboard. The switch between them is Command-Space.
I also have password requirement for waking up or going from screen saver.
Now if screensaver starts with non-English layout selected, I'm not able to login:
password is not accepted because keyboard layout is not English and switching
to English layout does not work in unlocking window.
Is there any way to change layout while in the unlock window?
Thanks

Yes you are right, this is not a bug, it's just bad user interface. Just imagine the following scenario...
Writing a paper, switching to Greek to enter a couple of characters and leaving the mac idle for 5 mins.
The lock screen comes up asking for a password, unfortunately the user didn't change the language
before the mac was left idle and there is no option to change the language in the lock screen.
User has to hard reset to access the mac and let's hope that the user was saving his paper frequenlty.
So from a coding point of view this is not a bug, but from a user interface design it is a huge flaw

Dwm and non-english keyboard layouts problem

Hi all,
I am using dwm 5.5. I'm Greek so I change between keyboard layouts all the time,
see the relevant xorg.conf section:
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,gr"
Option "XkbVariant" ","
Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
EndSection
Now the thing is that whenever I switch to Greek (by pressing Alt+Shift) the
dwm tags (1,2,...,9) are not clickable (keyboard shortcuts do work
though, so it's not a very big problem).
Do you have any ideas about how to fix that behavior? I'd go to the dwm irc
channel and ask them, but I'll be a "newbie asking stupid questions" so I
preferred to ask here
Thanks in advance
Last edited by geo909 (2010-01-08 17:23:29)

thayer wrote:Your best bet would be to post your problem to the dwm mailing list:
[email protected]
Will do...
Thanks!

MSI, please stop using non-standard keyboard layouts.

God dam it MSI, why do you insist on messing with layout of the bottom row of the keyboard?
You get everything else right, but for some reason when it comes to the bottom row of keys you want to say "Industry standards? 20 years of tradition? Fack that, we're gonna move things around for no facking reason."
Explain to me why you feel the need to put a superfluous "\" key on the keyboard to the right of the space bar. Nobody wanted that, nobody was asking for that, nobody needs that. Why the hell did you do that?
Explain why the Menu key is missing in action.
Explain why you put the Windows key on the wrong side. And while you're at it, explain why you thought this clusterfack of having that second "\" key there in combination with the missing menu key being not where it is on top of the Windows key being in the wrong place was a good idea.
Bottom row of a standard keyboard layout goes like this:
Ctrl, Fn, Alt, Win, Space bar, Alt, Win, Menu, Ctrl.
MSI layout goes like.
Ctrl, Fn, Alt Space Bar, \, Alt Gr, Win, Ctrl!
WHY?!
MSI seems to think that having the keys in the right place so my fingers will know where they are without having to learn key placement all over again is a horrible idea. Instead they seem to think that my fingers should need to relearn the god dam keyboard all over again for no reason at all.
But hey, at least the kept the numpad the same, right?
GOD DAM IT MSI!
Aparantly MSI logic works like this:
Everyone uses the numpad.
Nobody uses the trackpad to game.
Delete that numpad that everyone uses, insert fancy trackpad that nobody will use.
Profit?
What the hell are you people smoking?
Seriously, when is the last time you gamed on a PC with anything other than a mouse in your right* hand? Do you ever use the trackpad when you game? Ever? I own two laptops and I never, ever use the useless trackpad. I hate trackpads. First thing I do when I buy a new laptop? I plug in a mouse. Second thing I do? Disable the god dam trackpad.
*Some left-handed use of mice can occur. See nearest lefties for details. May contain nuts. For external use only.

I had a Gateway FX years ago that was a great laptop, but the "fn" key was at the bottom left instead of ctrl. I used that laptop for years and I was never able to become accustomed to it for gaming (group select ctrl+# ffs) or word processing, so I feel your pain.
That being said, you should be able to re-bind your keys without any problem, and possibly pop off the keys themselves and move them to their new locations if they're the same size and you like that consistency. You can rebind via the registry, or certain bios, or w/ a third party application.
The track pad is essential if you've got limited space and/or aren't a twitch gamer. For non-real time games, there is hardly any advantage to using a mouse over a good track pad.

Can't change the keyboard layout in Xorg

I tried the different possibilities in the wiki to change the keyboard layout in X. setxkbmap does work, but I'd like to keep the settings across reboots. I tried the two methods in the wiki, here are my config files:
/etc/X11/xorg.conf.d/00-keyboard.conf (created by localectl)
# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "de,ru"
Option "XkbModel" "pc104"
Option "XkbVariant" ","
Option "XkbOptions" "grp:alt_shift_toggle"
EndSection
/etc/X11/xorg.conf.d/10-keyboard.conf (manually created)
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "de,ru"
Option "XkbModel" "pc104"
Option "XkbVariant" ","
Option "XkbOptions" "grp:alt_shift_toggle"
EndSection
But the output of "setxkbmap -print -verbose 10" shows german and us-english layout:
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc104
layout: de,us
variant: ,
options: grp:alt_shift_toggle
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwertz)
types: complete
compat: complete
symbols: pc+de+us:2+inet(evdev)+group(alt_shift_toggle)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwertz)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+de+us:2+inet(evdev)+group(alt_shift_toggle)"};
xkb_geometry { include "pc(pc104)" };
Does anybody know what I am doing wrong? I would appreciate any help.
Thomas

In your .xinitrc file put setxkbmap yy & (yy=country code for example de) before it executes your de/wm.

Some applications don't put accents with non-english keyboard layouts

I'm using a Portuguese keyboard with three different macs running Mac OS Tiger 10.4.8/9. Some applications (like Motion 2 and Swift Publishing 2) don't allow writing some accented characters, like (è) or (ê), that are accessed by Shift+normal key, but they do display correctly other accented letters, for instance (é), witch are accessed directly without the Shift key. This happens only in some applications and with a european keyboard layout (I tried it also with the spanish and french keyboards layouts), but not with other applications (it works all right with Word or iPhoto) and the english keyboards.
Any sugestion as how to solve this? If I create the text in some other application and paste it in Motion it works! But it's a drag.
iMac Core2Duo 20" Mac OS X (10.4.8) MacBook Core2Duo MacPlus

Hey KDCruz,
Thanks for the question. Let's see if we can isolate the issue further, the following article has some great troubleshooting steps:
One or more keys on the keyboard do not respond
http://support.apple.com/kb/TS1381
Thanks,
Matt M.

Non-US keyboard layout problem with VNC

Hi everyone,
I've got an arch box at work running tigervnc through an ssh tunnel so that I can work from home when I need to.
Everything is great, as long as I'm using and ASCII keyboard layout.
When I switch layouts, the keystrokes just don't get through to the server.
Here's what I use to switch layouts:
setxkbmap -layout us,ru -option 'grp:alt_shift_toggle'
So I need to type in russian, and I hit alt-shift, as usual, and start typing, but nothing is echoed back to me. I can tell that the keystrokes are just not getting to the destination because if I'm at a terminal and I'm switched to the ru layout and I type something and hit enter, I just get a newline, as if there was nothing typed at all.
Any ideas?

Hi,
Why are the characters mixed up in the session?
This issue can occur if the keyboard language has been switched on the remote PC while running a remote desktop session. In the case you would like to switch to a different keyboard
language follow these instructions.
Important:
The remote PC selects the system language of the device running the remote desktop client and not the keyboard language. When switching the keyboard language on your device,
you need to manually switch the keyboard language on the remote PC.
1. Open settings on your device.
2. Tap General and then tap International.
3. Tap Language and select the language running on the remote PC.
4. Open the RD Client and connect to the remote PC and check if the Windows keyboard language matches the language that you selected.
Quote from
Remote Desktop Client on Mac: FAQ
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hotkeys do not work when non-english keyboard layout is active

I live in Russia and use Russian keyboard layout pretty frequently. Also, I am a big fan of using hotkeys. But the problem is that in any Aperture version, hotkeys only work when english/U.S. layout is active. It's pretty annoying to switch back and forth.

You can tell Apple how you want this fixed at
http://www.apple.com/feedback/aperture.html

[Solved] Add a single Spanish letter to my non-Spanish keyboard layout

Hi,
I correspond with Spanish speaking people a lot. They have some special letters like accented vocals (á, í, ó and the likes). I can enter those with my deadkeys accent followed by a vocal, even though my natural keyboard layout is German.
The only problem I have is the ñ. I'd love to have this mapped to AltGr+n. This combo is currently mapped to the weird character ”, which I don't really need.
My question: Using LXDE/openbox, how can I best map AltGr+n to the ñ character?
Thanks in advance,
Alex
Last edited by kilmister (2013-01-22 13:24:22)

This sounds like you really want to use xmodmap. If it's just one or two keys, I'd probably just assign them via direct xmodmap commands in your .xinitrc file.
First run `xmodmap -pke`, grepping for the key your want to modify. See the arch wiki page on xmodmap for the level you'll use: https://wiki.archlinux.org/index.php/Xmodmap
The you can call xmodmap for that single key as a test (example only from my own xmodmap -pke output):
xmodmap -e "keycode 38 = a A Greek_alpha Greek_ALPHA aacute Aacute"
So you could change the Greek_alpha in this case to an uppercase Q:
xmodmap -e "keycode 38 = a A Q Greek_ALPHA aacute Aacute"
If it's just one or two changes I find it easier to use `xmodmap -e ...` in .xinitrc rather than create an entirely new xmodmap file to use.

[SOLVED] Keyboard layout in xorg 1.9

I'm trying to add a Romanian layout and I don't know how.
Most of the topics I've seen are OLD. They may or may not've worked with previous xorg versions, I don't know. They certainly didn't for me.
Please help.
Here's my xorg.conf:
# Section "ServerFlags"
# Option "ignoreABI" "True"
# EndSection
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "gb,ro"
Option "XkbOptions" "grp:caps_toggle,grp_led:scroll"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 150.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nouveau"
VendorName "nVidia Geforce 7025"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "DynamicTwinView" "false"
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Adding this didn't help:
Option "XkbLayout" "gb,ro"
Option "XkbOptions" "grp:caps_toggle,grp_led:scroll"
Last edited by DSpider (2012-02-17 08:37:46)

The kind people from the IRC channel suggested I add this bit at the very end of the "/etc/X11/xorg.conf" file (instead of "/etc/X11/xorg.conf.d/10-evdev.conf" - tho it would've probably worked that way too):
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "us, ro"
Option "XkbVariant" "std"
Option "XkbOptions" "grp:caps_toggle, grp_led:scroll"
EndSection
Apparently it works. I just have to hold AltGr and press s, q , a, i, t, etc to type ș â ă î ț etc. But how do I set it to ; { } ] ' ", etc, like the default behaviour in Windows... ? I would like them to correspond to this layout.
Because this is not the "standard" ("std") version...
I may have to edit the "/usr/share/X11/xkb/symbols/ro" file to map them.
Unless there's a better way ?
Last edited by DSpider (2010-12-11 13:19:16)

[SOLVED] Awesome 3.5 using english keyboard layout instead of Xorg's

Keyboard layout was OK on 3.4.
For 3.5 and git version, Awesome defaults to english layout. Calling awesome.restart() (e.g. with SUPER+SHIFT+R) will correctly set the layout according to Xorg config. That's quite annoying indeed.
Only Awesome is affected, i.e. all other applications will use the Xorg config. So basically the affected parts are
* key bindings
* Run command
* Run lua code
Using
* up to date x86_64 system
* blank user session
* startx and 'exec awesome' as the sole command.
I couldn't find any related issue on the web, seems strange to me since I shouldn't be the only one using a non-english keyboard layout !
Any idea ?
Last edited by Ambrevar (2013-08-02 20:01:32)

Same here, but as with nomorewindows case, I just need to restart awesome, but I need to do it every time I boot. Both my console and X are configured to dvorak, but in X it's set through .xinitrc.
I'm going to try and see whether putting
echo "awesome.restart()" | awesome-client
into my .xinitrc will help.
By the way, my .xinitrc starts awesome in the following way:
awesome & wmpid=$!
[whole bunch of misery involving mpd, urxvt and setting the keymap in X]
[above for restarting awesome]
wait $wmpid

Non-US keyboard layout in Xorg

Similar Messages

Maybe you are looking for