Problem on Linux Mint with non-standard keyboard layout

[AlexTP]

Yandex translate of feedback of CudaText's user post:

I installed a deb package for my system (Mint Cinnamon), but apparently I'm not destined to use the editor. The reason is the same as in Sublime - the editor ignores the current system keyboard layout. It doesn't matter as long as the standard layout is used. But this is not my case…

A bad feeling arose immediately when I read "Better support national keyboards on Linux" on the page at the suggested link https://wiki.freepascal.org/CudaText#Advantages_over_Sublime_Text_3 Oh, it doesn't bode well for breaking the Unix-way: "A program should do ONE thing, but do it well." There is also the xkb module, which deals with all issues related to keyboard layouts. Don't do "better support keyboards"! Let the specialists working on xkb do this. Keyboard layouts are a much deeper topic than it might seem at first glance.

As I imagine the problem from a technical point of view — it is necessary to process the keycodes proposed by the system (together with the state of the modifiers), and not try to interpret the scancodes received from the keyboard independently. But I could be wrong here.

Switching the layout to the standard one, I was able to experiment a little with the editor.

[Thaddy]

mint is not so mint....

[Seenkao]

Боюсь это проблема Linux, но ни как не сторонних приложений и наборов.
Возможно решение: сменить Wayland на XOrg и/или обратно. Я сталкивался с подобным в MacOS. Даже с указанием какая у меня клавиатура, всё равно могло быть не соответствие с выводимой кодировкой.
В некоторых случаях на это можно "забить", если это не критично.

Yandex translate:
I'm afraid this is a Linux problem, but not third-party applications and kits.
Possible solution: change Wayland to XOrg and/or vice versa. I have come across similar in Mac OS. Even with the indication of which keyboard I have, there could still be a discrepancy with the output encoding.
In some cases, it can be "scored" if it is not critical.

[AlexTP]

More details from that user. Quote:
I have my own table that sets the correspondence of keys and symbols. Like Dvorak, Kolemak or Burman, but different.

Technically, I set all these parameters en masse, via keymap:

Code: Bash  [Select][+][-]

1. xkb_keymap {
2.     xkb_keycodes  { include "evdev+aliases(qwerty)" };
3.     xkb_types     { include "complete+four_levels+four_levels_numpad" };
4.     xkb_compat    { include "complete" };
5.     xkb_symbols   { include "pc+inet(evdev)+happy-typist(numblock)+happy-typist(latin)+happy-typist(russian):2+happy-typist(switchers)+happy-typist(switchers):2" };
6. };
7.  

Then, in one script, it runs something like this:

Code: Bash  [Select][+][-]

1. xkbcomp -I "~/Administration/xkb" "keymap/my_layout" "$DISPLAY" &>>"debug/log.txt"
2.  

[af0815]

https://www.daskeyboard.com/blog/qwerty-vs-dvorak-vs-colemak-keyboard-layouts/
gives some info about the different layouts. Another group are input methods for people which special needs.

Now i slowly understand the discussion.