-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux: Using non-US keyboard layouts makes special characters come up wrong. #298
Comments
It's weird that it is happening if the layout is set to Finnish before starting Plover. Can you try with the current Git master? Changing layouts while Plover is running will not work, but I'm working on a fix. |
Tested with
Before I ran "python launch.py", I made sure that I definitely had Finnish keyboard layout active. Still, I experienced the same problem. |
OK, can you give me the output of |
Here are the outputs of xmodmap with the layouts:
A funny thing, that I just noticed is that some characters seemed to behave right. Such as the colon (:) or the equal sign (=). Which I have defined as "ST-L": "=",
"TP-PBLG": "{^:}", Could it have something to do with the fact that the pipe character needs to be typed with the "Alt Gr" or the Actually I have Here's the diff of the file: @@ -260,6 +205,8 @@ class KeyboardEmulation(object):
"""Prepare to emulate keyboard events."""
self.display = display.Display()
self.modifier_mapping = self.display.get_modifier_mapping()
+ # Load non-us keyboard related keysyms.
+ XK.load_keysym_group('xkb')
# Determine the backspace keycode.
backspace_keysym = XK.string_to_keysym('BackSpace') |
AFAIK, using As for handling "Alt Gr" combos, that's why I asked you to try with the latest Git, because I added support for it: cbedcb2 |
Our handling of groups is wrong, looking into it... |
So, bad news, bad news... Without proper support for the XKB extension, there is not way to correctly handle groups... Even worse, the current support for "Alt Gr" combos will not work if more than 1 group is used:
|
For this issue, if we can at least get to a point where our limitations are defined and we are better off than the current situation, then we can at least claim an improvement. I'd like to have this in for Plover next. |
The way I have gotten the pipe symbol working is by defining a dictionary entry:
Where the ISO_Level3_shift key as a meta key is enabled by the This is, of course, not even close to the solution and these kind of entries make the dictionaries keyboard layout specific but it was the only way I was able to get the pipe symbol working with the Finnish keyboard layout. |
@benoit-pierre It reads like you have a good understanding of this issue. Is there a solution possible, even if it's one we can't readily implement just now? |
We need XKB support in |
Duplicate of #650. |
I'm using Plover on a Linux computer (Ubuntu 15.04) and I noticed that the Plover is somehow affected by the active keyboard layout. For example, I if press PAOEUP which mapped to "{^|^}" while I have the US keyboard selected I get the normal pipe symbol (|). If I, however, have the Finnish keyboard, which is what I usually use all the time, I get the asterisk ().
It seems that Plover is effectively press the key left to enter-key with shift down. On the U.S. keyboard layout it creates the pipe symbol, but on the Finnish keyboard layout it is mapped to the asterisk.
This problem occurs even though I have the Finnish keyboard layout selected when I start Plover.
The text was updated successfully, but these errors were encountered: