5974d989fe
* `UC_MOD`/`UC_RMOD` -> `UC_NEXT`/`UC_PREV` * `UNICODE_MODE_*` -> `QK_UNICODE_MODE_*` * `UC_MAC` -> `UNICODE_MODE_MACOS` * `UC_LNX` -> `UNICODE_MODE_LINUX` * `UC_WIN` -> `UNICODE_MODE_WINDOWS` * `UC_BSD` -> `UNICODE_MODE_BSD` * `UC_WINC` -> `UNICODE_MODE_WINCOMPOSE` * `UC_EMACS` -> `UNICODE_MODE_EMACS` * `UC__COUNT` -> `UNICODE_MODE_COUNT` * `UC_M_MA` -> `UC_MAC` * `UC_M_LN` -> `UC_LINX` * `UC_M_WI` -> `UC_WIN` * `UC_M_BS` -> `UC_BSD` * `UC_M_WC` -> `UC_WINC` * `UC_M_EM` -> `UC_EMAC` * Docs * Update quantum/unicode/unicode.h |
||
|---|---|---|
| .. | ||
| config.h | ||
| readme.md | ||
| rules.mk | ||
| rverst.c | ||
| rverst.h | ||
| unicode.h | ||
readme.md
Overview
This is my user space, main goal is to unify the experience between different keyboard models and operating systems. My native language is German and I almost exclusively use keyboards in the US-ANSI layout. I find this layout the most practical for programming as far as the placement of special characters is concerned. However, when I write in German, I miss a few special characters like umlauts, etc. Since I also use different operating systems (MacOS, Linux and Windows) and especially Windows and MacOS behave very differently regarding the input of such characters (under Linux there is at least the Compose key). So I needed a hardware solution, and that's how I came to QMK.
Here are defined some key codes to put the keyboard in different modes (Mac, Windows, Linux) and the corresponding functions to make the input. And some logic to store the respective mode and load it at boot time.
You'll find a proper layout here: keyborads/id80/keymaps/rverst