- Jun 08, 2021
-
-
Sergey Udaltsov authored
-
Sergey Udaltsov authored
-
- Jun 05, 2021
-
-
-
SHIFT+Page_Up, SHIFT+Home, etc are a very useful sequence keyboards in KDE, so when I press SHIFT+Page_Up and when Page_Up is on keypad, gives number 9 and is a very disapointing. For example in konsole, I use a lot SHIFT+Page_Up and SHIFT+Page_Down to scroll the screen up and down. After reasearch a lot if just not swap from base to number when press SHIFT, while SHIFT+number is not problem send the base key solves the problem in a very simple way I found a similar request on this topic https://bbs.archlinux.org/viewtopic.php?id=257020 from where I based myself to find the solution.
-
- Jun 04, 2021
-
-
Joshua Cogliati authored
This allows the letters with a breve to be typed in English (Dvorak) and English (Dvorak, alt. intl.)
-
- May 29, 2021
-
-
Saadat Mateen authored
-
- May 20, 2021
-
-
Peter Hutterer authored
This lets us use the ci-fairy image instead of manually preparing the alpine image on each run. Side-effect: we won't fall afoul of docker's pull limits. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
- May 19, 2021
-
-
Richard Gomes authored
-
-
-
-
The new extended layout variant named us(cz_sk_pl_de_es_fi_sv) and is targeted to Czech and Slovak polyglots and SW engineers (like the original one). Proposed layout is the result of the discussion among Polyglot Gathering community of polyglots (https://www.polyglotgathering.com/ ). Signed-off-by: Vitalii Chernookyi <vitaly.v.ch@gmail.com>
-
-
- May 04, 2021
-
-
qwertfisch authored
The defined character differs from the official Neo reference and should be a fraction slash (U+2044).
-
- Apr 27, 2021
-
-
Peter Hutterer authored
There doesn't seem to be a 639 code of "inc", so let's default to "eng" because that is what is suggested here and I don't know any better: https://github.com/NiranjanTambe/Indic-IPA Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
These very much look like invented ones... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The extras used some of 639-2/B, let's make this consistent across both files. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
It's just the DTD file, not an XML document itself. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
console-setup still relies on the xorg ruleset [1] and there may be other tools out there. Let's provide an equivalent option to our autotools build to install the xorg symlinks. Note that unlike the autotools approach, only the "xorg" symlinks are provided, not the well and truly legacy "xfree86" ones. [1] https://salsa.debian.org/installer-team/console-setup/-/merge_requests/7/ Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 23, 2021
-
-
Peter Hutterer authored
libxkbcommon (commit 1cae25005211) now provides the output of the layout tester format in YAML, with successful compilations on stdout and failed ones on stderr. This makes it easy to collect the results, extract and print the failures with yq but also parse the yaml file and leave a JUnit XML in place that will then show up as result on a MR page. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 21, 2021
-
-
Peter Hutterer authored
Just "Using ." or whatever the env is set to is not helpful, let's make this message more useful. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Jason Francis authored
-
- Apr 16, 2021
-
-
-
Peter Hutterer authored
It causes the CI job to fail because diff now finds something that changed. See d1a7abd3 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 14, 2021
-
-
Fix typos (mainly capitalization) to improve consistency in naming of layouts
-
- Apr 12, 2021
-
-
These don't need to sit in the main source tree where we need exceptions for them in the build system. They are only called from special jobs in the CI pipelines, so let's move this to the CI directory. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
No functional effect but it makes simple parsers easier and grep more reliable. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 08, 2021
-
-
Hans de Goede authored
Nowadays the default keyboard sold in The Netherlands uses the standard US layout with a euro-symbol on the 5 key. Add a "Dutch (US)" variant, which is just an alias for "us(euro)" for this. Link: xkeyboard-config/xkeyboard-config!198 Signed-off-by: Hans de Goede <hdegoede@redhat.com>
-
Hans de Goede authored
In Europe some users may prefer to use an English (US) keyboard layout over their country's native layout, there is enough demand for this that keyboards with the English (US) layout are sold all over Europe. In some countries (e.g. The Netherlands) the English (US) layout is even the default layout. The English (US) keyboards sold in Europe will have a euro-sign on the 5 key and in most cases they use the ISO physical-keyboard-layout which has an extra 102nd key between the left Shift and the Z key. This extra key is marked as a second backslash/bar key. Before this commit the `us(euro)` variant did not contain a specific binding for the `LSGT` key, so it inherited the standard less/greater binding from the pc105 symbols, resulting in the key sending the wrong symbols. Add a `LSGT` key binding to backslash/bar to the `us(euro)` variant to fix this. Note under Windows even the `us(basic)` variant has the `LSGT` key bound to backslash/bar, but a lot of XKB layouts inherit from the `us(basic)` variant so changing it there will cause problems elsewhere. Link: xkeyboard-config/xkeyboard-config!198 Signed-off-by: Hans de Goede <hdegoede@redhat.com>
-
Hans de Goede authored
Move some lang(us) variants from us(euro) to us(basic) as basis, adding the: include "level3(ralt_switch)" include "eurosign(5)" To the changed over variants (where not already present) so that there are no functional changes. This is a preparation patch for changing the mapping of LSGT to backslash/bar in the "us(euro)" variant. First making sure that no other variants derive from the "us(euro)" variant, ensures that this change will not impact any other variants. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
-
- Apr 06, 2021
-
-
Peter Hutterer authored
Follow-up from !172, introduced in 2a0c538c Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 31, 2021
-
-
-
-
For the old behaviour, use `setxkbmap -option lv3:ralt_switch_multikey`
-
- Mar 23, 2021
-
-
Peter Hutterer authored
These were added as comments only, presumably to reserve the key for future updates. They are now mapped as part of the autogenerated keysym range and we can remove these comments. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
These symbols were added manually but are now autogenerate from the protocol headers. To simplify the symbols table, drop the manually added ones and let them be autogenerated - this way we need less duplicate detection and the symbols themselves are in-order with the rest. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
xorgproto 2021.2 and later has a recognizable pattern for adding new keysyms to XF86keysym.h based on the Linux kernel input-event-codes.h. Use this to detect any keysyms that are present in the header file but not yet in symbols/inet. This is merely a gitlab CI job as we only have to do an actual update once every few months or so. A git diff is sufficient here too, it contains all the information we will need to understand what is missing from the updated file. We check xorgproto master because that gives us some heads-up on what will come. There is a minor chance that we are mapping keycodes that change before the release but it's minor and fixable anyway. Requires: xorg/proto/xorgproto!23 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 17, 2021
-
-
Peter Hutterer authored
This layout does not exist and we will never provide it. However, having it in the XML file means it will show up in GUI configuration mechansism that parse the XML file directly (instead of using libxbkcommon's libxkbregistry). Our rulesets fall back to the file "symbols/layout", section "variant" for any layout(variant) that's not explicitly covered. This enables users to create a symbols/custom file with their layout and have it available. As there are no variants, the GUI tools will only be able to use the default section. Commandline tools can use variants as well. This is papering over the whole issue only, but it does provide for some convenience. It will still require adding a file in /usr/share in most cases, but since we do not provide this file, it will be safe from being overwritten. Fixes #257 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-