Bug #11034

Keyboard shortcuts & non-US keyboard layouts

Added by Van de Bugger almost 4 years ago. Updated over 3 years ago.

Closed: won't fix
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
hardware architecture:


This is a usability issue.

I have two keyboard layouts, the first one is en_US, the second one is not (it is non-latin-based). Some keyboard shortcuts like z, d, l, etc do not work if the second keyboard layout is activate.

It seems only plain keys with no modifiers are affected. For example, Ctrl+t works in both layouts. (Also I am not sure if this problem is specific for Fedora and/or Linux in general.)

Ideally, keyboard shortcuts should be keys, not characters, so pressing z key shows the image regardless of current keyboard layout and generated character.

If this is not possible, darktable should allow to assign multiple keys to the same action. It is an ugly workaround, but it is better than nothing.


#1 Updated by Tobias Ellinghaus almost 4 years ago

It used to be like that. It was terrible.

You can keep two copies of ~/.config/darktable/keyboardrc and put them in place when using a different keyboard layout.

#2 Updated by Van de Bugger almost 4 years ago

You can keep two copies of ~/.config/darktable/keyboardrc…

Probably I was not clear. I have two (or more) keyboard layouts for two (or more) different languages, e. g. English and Russian (or English and Greek and Hebrew, etc). Keyboard layouts are changed by a dedicated shortcut (e. g. Super+Space in Gnome Shell). It is not feasible to leave and restart darktable each time I switch keyboard layout (= language). Depending on the target audience, I may fill in the metadata (or tags) in either English or non-English language.

Thus, two copies of keyboardrc do not work. I tried to specify two shortcuts for the same action. e. g.:

(gtk_accel_path "<Darktable>/views/darkroom/full preview" "z")
(gtk_accel_path "<Darktable>/views/darkroom/full preview" "я")

But it seems it does not work also: the later assignment overrides the previous.

#3 Updated by Tobias Ellinghaus almost 4 years ago

  • Status changed from New to Closed: won't fix

I see. Well, I fear that's too much an edge case to justify all the problems it would bring.

#4 Updated by Roman Lebedev over 3 years ago

  • Target version set to 2.2.0

Also available in: Atom PDF

Go to top