summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* add a missing comma to the name of a niche layout, to match similar namesHEADmasterBenno Schulenberg2023-05-173-3/+3
|
* symbols/et: use dead-vowel symbols instead of mistaken Unicode codepointsBenno Schulenberg2023-05-171-6/+6
| | | | | | | | | | | | | | | | | When twelve years ago, in commit c28367a15, the code points 0x100FE67 and further were added for "dead a" and such, the intention was that they were raw key codes (0xfe67 and further), not Unicode codepoints. See the original patch that requested adding very similar key codes to xorgproto three years earlier: https://bugs.freedesktop.org/attachment.cgi?id=18679 The compose sequences in libX11 have been updated to use the dead-vowel symbols instead of the erroneous Unicode codepoints (most of which are valid codepoints for certain characters, that thus became unusable in the Amharic locale), so now it's time to update the keyboard layout. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* correct the name of the Russian layout for a Czech keyboardBenno Schulenberg2023-05-172-2/+2
| | | | All other such layouts are named in this manner: Language (Country).
* symbols/ancient: make Ugaritic the default ancient layoutBenno Schulenberg2023-05-151-1/+1
| | | | | For most people a cuneiform script like Ugaritic is more likely to represent the "canonical" ancient script than something like Gothic.
* rules: match the phrasing for the 5th-level chooser with the two othersBenno Schulenberg2023-05-151-1/+1
| | | | | | | | Six years ago, commit 10cf5acd90 added the word "the" in the phrase "Key to choose the 3rd level", but not in its sister phrase, the one for the 5th-level chooser. To compare, run: `grep -R "Key to choose"`
* Tests: improve keycode checkPierre Le Marre2023-05-091-2/+23
|
* CI: improve xkbcommon artifactPierre Le Marre2023-05-091-13/+27
|
* adjust the wording of some comments in the regression-test scriptBenno Schulenberg2023-05-041-11/+11
| | | | | Fix spelling, add helpful little word, s/pressing/releasing/, drop duplicate word, and improve punctuation.
* Add regression testsPierre Le Marre2023-05-023-18/+880
| | | | | | | | | | - Create Python bindings to xkbcommon. - Create a regression test framework using pytest. - Add regression tests for issues 90, 346, 382 and 383. - Document how to write tests. - CI: Create a separate job for the libxkbcommon build that share its artifacts. - CI: Add the tests to the keymap_tests job.
* build: allow any blanks between file and variant names, not just tabsBenno Schulenberg2023-04-301-3/+2
|
* make the name of the Gagauz layout conform to "Language (Country)" formatBenno Schulenberg2023-04-292-2/+2
|
* symbols/ca: restore a redefinition that was dropped by misunderstandingBenno Schulenberg2023-04-291-0/+2
| | | | | | | | Four days ago commit 43a420f003 dropped the redefinition of `AB09` from the Canadian OLPC layout, thinking that the Unicode HYPHEN (U+2010) is the same as keysym 'hyphen'. But the latter is U+00AD, the SOFT HYPHEN. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* symbols/md: correct a name, drop an unneeded include, reshuffle a lineBenno Schulenberg2023-04-291-61/+57
| | | | | Also, adjust some whitespace, delete two stray characters from the "graphical" representation, correct one, and add a missing one.
* symbols/al: reshuffle a definition, shrink whitespaceBenno Schulenberg2023-04-291-103/+103
| | | | Also, replace two Unnnn codes with the corresponding symbolic names.
* rules/compat: delete more old remappingsBenno Schulenberg2023-04-291-10/+0
| | | | (This should have been part of commit db45bd75 from four days ago.)
* CI: fix yaml-to-junit-xml scriptPierre Le Marre2023-04-272-3/+18
| | | | Additionally, report successful tests count.
* CI: add new workflow rulesPeter Hutterer2023-04-281-0/+6
| | | | | | | Required to run pipelines after some infrastructure changes, see https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/540 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* move the Avestan layout from the Persian file to the Ancient fileBenno Schulenberg2023-04-274-91/+69
|
* move the Ugaritic layout from the Arab file to the Ancient fileBenno Schulenberg2023-04-274-67/+74
|
* add a layout for the Gothic scriptBenno Schulenberg2023-04-273-0/+100
| | | | | | | | | | | | | | | This Gothic layout is put in a new symbols file, called 'ancient', so that there will be a place for other layouts for antique scripts. The name "ancient" is chosen because that is how Gothic is marked in https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes. This fulfills issue #55. Proposed-by: Tim Nelson Original-patch-by: Tim Nelson Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* types/level5: correct two specifications, to not swap levels 3 and 4Benno Schulenberg2023-04-271-2/+2
| | | | | | | | | | | | | | Just like Lock does not swap levels 3 and 4 when just LevelThree and maybe Shift are in effect for EIGHT_LEVEL_ALPHABETIC_WITH_LEVEL5_LOCK, Lock should *also* not swap those levels when also the LevelFive-Lock (NumLock) *and* LevelFive itself are in effect. This fixes issue #381. Problem existed since the EIGHT_LEVEL_ALPHABETIC_WITH_LEVEL5_LOCK type was introduced, in commit 39124ccf14, thirteen years ago. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* rules/compat: delete some remappings that are more than fifteen years oldBenno Schulenberg2023-04-251-14/+0
| | | | Users have had enough time to get used to the new names.
* symbols: give the remaining country files a good header lineBenno Schulenberg2023-04-2518-47/+55
|
* symbols/ca: condense whitespace, use Unnnn codes, improve alignmentBenno Schulenberg2023-04-251-209/+208
| | | | Also reshuffle three keys into order, and drop an unneeded redefinition.
* symbols/th: use an include instead of repeating almost an entire layoutBenno Schulenberg2023-04-251-45/+2
|
* symbols/th: trim obsolete comments, use Unnnn codes, shrink whitespaceBenno Schulenberg2023-04-251-217/+212
|
* symbols/la: use Unnnn codes, shrink whitespace, trim commentsBenno Schulenberg2023-04-251-118/+113
|
* symbols/ie: reshuffle keys into normal order, use shorter Unnnn codesBenno Schulenberg2023-04-251-220/+216
|
* symbols/ie: trim superfluous comments, replace a few 0x100nnnn codesBenno Schulenberg2023-04-251-89/+21
|
* symbols: miscellaneous small editsBenno Schulenberg2023-04-256-27/+28
|
* symbols/ch: add three symbols (on Mac) that comments say should be thereBenno Schulenberg2023-04-251-12/+9
| | | | Also delete three pointless NoSymbol specifications, and tweak comments.
* symbols/ch: improve alignment, shrink whitespace, unwrap definitionsBenno Schulenberg2023-04-251-115/+114
| | | | Also, reshuffle a few keys into their normal order.
* symbols/gh: improve alignment, shorten to Unnnn codes, shrink whitespaceBenno Schulenberg2023-04-251-74/+90
| | | | Also add comments after the Unnnn codes, and drop redundant includes.
* improve the names of two Czech and two Slovak variantsBenno Schulenberg2023-04-253-14/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Nineteen years ago, commit 8e1e2d8195 baptized these four variants with the words "extended backslash". Nine months later, commit 999e981f4c synced these names to the relevant symbol files. But just two days later, commit 3ad7cee7c5 changed one of the names to read "with <\|> key", in response to https://bugs.freedesktop.org/2319. (A week later, commit 1b8556fe6f synced this name to the XML file.) This gave one of the four very similar variants a deviant name. The string "with <\|> key" is difficult for translators. For a long time I have thought that "<" and ">" were the relevant symbols, and that the "|" was an OR symbol, escaped by the "\". In other words: I thought that the string referred to the LSGT key. :/ What the four variants actually do is: put the backslash and vertical bar characters on the BKSL key (replacing the dead diaeresis and the apostrophe), for those keyboards that lack the LSGT key, to make typing "\" and "|" more straightforward -- these symbols are present also on the third level of the Q and W keys. So what those variants do is: add an *extra* backslash and vertical bar character to the layout, for easier access, at the cost of having the apostrophe accessible only via AltGr and the dead diaeresis only via Shift+AltGr. So... name all four variants more fittingly and in the same manner. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* rules: make the `Shifts` group toggle override any layout's Shift keysBenno Schulenberg2023-04-247-3/+7
| | | | | | | | | | | | | | In order to make the option `grp:shifts_toggle` effective also with the few layouts that define the Shift keys too, the option should be applied to each group separately, and the option should specify the key type explicitly. This fixes issue #380. Problem existed since the T3 layout was added in 2013, and worsened when the E1 layout was added in 2020. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* symbols/group: leave two first levels undefined, to allow combiningBenno Schulenberg2023-04-241-6/+4
| | | | | | | | | | | | Many people do not need the CapsLock functionality, so leaving the first level of the `<CAPS>` key undefined in these two options allows users to combine `grp:shift_caps_toggle` or `grp:alt_caps_toggle` with most of the one-level `caps:` options, for more versatility. (Because of the order of the rules, any `caps:` option will be applied first, and then the `grp:` option will add a second level.) Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* rules: harmonize whitespace to tabs and improve alignmentBenno Schulenberg2023-04-231-120/+120
|
* rules: group the options for level3, keypad, and sundry things togetherBenno Schulenberg2023-04-231-37/+39
| | | | | | | | | | This looks better and should mostly have no effect as the options are largely independent. Only the moved `lv3:` options will now overrule some of the `caps:`, `ctrl:` and `compose:` options, instead of being overruled by them. In my opinion this is more consistent: all level3 options overrule most other options. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* rules: put also the general `grp:` rules last, so they overrule othersBenno Schulenberg2023-04-231-38/+38
| | | | | | | | | | Arguably, when options conflict, the group-switching options should overrule others, because when one has multiple groups one definitely wants to be able to switch. This fixes issue #384. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* revert commit 1cb7181936 plus the offending part of a1d41a4ef6Benno Schulenberg2023-04-212-7/+7
| | | | | | | | | | | | | Mapping modifiers to keys instead of to symbols causes problems when those keys carry symbols that are associated with *other* modifiers, as this leads to two or more modifiers getting linked together and thus activated in unison -- which one normally doesn't want. This fixes issue #382. (Issue #81 will have to be addressed in some other way.) Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* rules: put the `grp:` rules last, as they should have the last wordBenno Schulenberg2023-04-205-15/+15
| | | | | | | | | | | | When using a `grp:` option, one doesn't want other options to interfere with this option, so the rules for `grp:` options should come last in the list. This fixes issue #383. Reported-by: Sergey Stolyarov Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* Add U+06C0 to the Persian layoutcs1272023-04-181-2/+3
| | | | | | | | | | | In Persian, an isolated form of the letter Ye is added after nouns that are connected to adjectives, and if the noun ends with the letter He, it is often merged with the following Ye, into the letter He with Ye above (U+06C0). This character exists on the second level of AC05 in the Persian layout of Microsoft Windows, but not in the standard layout. This commit extends the standard layout to include U+06C0 on the third level of AC05.
* symbols: map three real modifiers to keys instead of to symbolsBenno Schulenberg2023-04-183-12/+18
| | | | | | | | | | | | Mapping a modifier to a symbol had the tiny advantage of not needing to explicitly specify a modifier mapping when putting the symbol onto some other key through some option. But it had the disadvantage of risking to lose the modifier mapping for the original key when the other key was just an addition and not a replacement. This generalizes the fix from the previous commit. Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* symbols/pc: map the Super modifier to the LWIN/RWIN keys, not to symbolsBenno Schulenberg2023-04-181-1/+1
| | | | | | | | | | | | | | | | | When a modifier is mapped to a symbol, then it will effectively be mapped to the first-found key that contains the relevant symbol, and that key might not be the key that the modifier is usually mapped to, leaving this latter key without a mapping. So, map the Super modifier to `<LWIN>` and `<RWIN>` instead of to `Super_L` and `Super_R` -- the Windows keys will then not lack their Super modifier when some other key is made into a Super key too. This fixes issue #81. Reported-by: Josh Triplett Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
* symbols/tj: condense comments, reshuffle keys into their normal orderBenno Schulenberg2023-04-121-119/+116
|
* symbols/jp: order the two main layouts first, the three options lastBenno Schulenberg2023-04-121-36/+37
|
* symbols/jp: improve comments, unwrap key definitions, harmonize blanksBenno Schulenberg2023-04-121-208/+189
|
* compat,types: harmonize some whitespace, and reshuffle some linesBenno Schulenberg2023-04-118-29/+32
| | | | Also, add some level specifications for clarity, although unneeded.
* symbols/level*: contract each key definition onto one line, when possibleBenno Schulenberg2023-04-103-147/+61
| | | | | | | This makes it easier to see where which symbols are assigned to a key when grepping for its code. Also improve a couple of comments.
* symbols/ro: improve some comments, and tighten the alignment a bitBenno Schulenberg2023-04-101-130/+138
|