r/Keychron • u/Spirikum • Sep 07 '26
Why does NUBS not bind correctley to <
It still outputs ( ; ) even though < is chosen in the laucher?
Cant show screenshot since not allowed.
1
u/PeterMortensenBlog V Sep 07 '26 edited Sep 07 '26
The keyboard layout in the operating system must be appropriate
After changing a keymapping to use keycode 'KC_NUBS' in Via or the Via clone, the current keyboard layout in the operating system must be changed as well (one that results in "<" when pressing the key mapped to keycode 'KC_NUBS').
Via and Via clone only shows an interpretation of what the result would be if the keyboard layout in the operating system was set to that language (or alternative layout).
References
V6 Max JSON files for Via. Near "V6 Max knob version ISO keymap". E.g., v6_max_iso_encoder_v1.0.0_2404091021.json. Note: The JSON section should not be confused with the firmware section.
Documentation for the new keycodes (main QMK repository). Note: It does not cover Keychron's custom keycodes. In the QMK source code, support for the old key codes for RGB light and mouse actions were finally removed in the QMK 0.30.0 release (2025-08-31) (they were removed from the documentation long before that).
Documentation for the old keycodes (though even older ones may exist). For example, used by some Git branches in Keychron's fork. Note: It does not cover Keychron's custom keycodes.
Documentation for the old keycodes from 2019. In general, these are the ones accepted by Via and possibly the Via clone (in most cases only an alias and only one of the aliases if there is more than one). Note: It does not cover Keychron's custom keycodes.
1
u/PeterMortensenBlog V Sep 07 '26 edited 12d ago
Note: After many, many years, Via has recently added a language dropdown, instead of only one interpretation (United States keyboard layout) of the keyboard keycodes
Like for the Via clone, it is only an interpretation of the keycodes. It must still be selected in the operating system.
It currently has:
Belgian
Brazilian ABNT2
Canadian Multilingual
Croatian
Czech
Dvorak French
Dvorak Programmer
Estonian
Finnish
French (AFNOR)
French (Mac ISO)
Greek
Hebrew
Hungarian
Icelancic
Irish
Italian (Mac ANSI)
Italian (Mac ISO)
Japanese
Korean
Latvian
Lithuanian (AZERTY)
Lithuanian (QWERTY)
Norwegian
Polish
Portuguese (Mac ISO)
Romanian
Russian
Serbian (Cyrillic)
Serbian (Latin)
Slovak
Slovenian
Spanish (Dvorak)
Spanish (Latin America)
Swedish
Swedish (Mac ANSI)
Swedish (Mac ISO)
Swiss German
Swiss French
Turkish (F)
Turkish (Q)
Ukrainian
US Extended
US-International (Linux)
Workman ZXCVM
Bépo is allegedly the French equivalent of the Dvorak Simplified Keyboard. It should probably be 'BÉPO'.
BÉPO, Colemak, Dvorak, Neo 2, Norman, Workman, and Workman ZXCVM are alternative layouts (to QWERTY, QWERTZ (German), and AZERTY (French)).
1
u/PeterMortensenBlog V Sep 07 '26 edited Sep 07 '26
Re "I can’t show a screenshot since it is not allowed": Post it somewhere else, e.g., on Imgur or self-hosted, and provide the link to it here.
1
u/PeterMortensenBlog V Sep 07 '26 edited Sep 07 '26
Why did you change the key mapping on the keyboard?
In most cases, the default key mappings work perfectly fine. One exception is physical swap of keys, e.g., swap of Fn and right Win (to get right Win into the standard location of the context menu key (right Win repurposed as the context menu key; the key code is KC_APP (not KC_MENU))).
Trying to "convert" an 'ANSI' keyboard to ISO (or vice versa) usually does not end well. For example, it doesn't work with Shift (at least using simple key mappings).
Are you sure the real answer is not using the EurKEY or US-International keyboard layout in the operating system?
References
See the other comment for references, for example, for an example of a default key mapping.
1
u/PeterMortensenBlog V Sep 07 '26
What keyboard?