From 509a2b40b798fd79a9d78b65e4daeb78cecf17ea Mon Sep 17 00:00:00 2001 From: Joel Challis Date: Mon, 9 Oct 2023 23:16:54 +0100 Subject: Fix old usage of UNICODE_MODE_MAC (#22238) --- docs/feature_unicode.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/feature_unicode.md') diff --git a/docs/feature_unicode.md b/docs/feature_unicode.md index 341084f926..2c6d2ef002 100644 --- a/docs/feature_unicode.md +++ b/docs/feature_unicode.md @@ -140,7 +140,7 @@ To set the list of enabled input modes, add the `UNICODE_SELECTED_MODES` define ```c #define UNICODE_SELECTED_MODES UNICODE_MODE_LINUX // or -#define UNICODE_SELECTED_MODES UNICODE_MODE_MAC, UNICODE_MODE_WINCOMPOSE +#define UNICODE_SELECTED_MODES UNICODE_MODE_MACOS, UNICODE_MODE_WINCOMPOSE ``` These modes can then be cycled through using the `UC_NEXT` and `UC_PREV` keycodes. You can also switch to any input mode, even if it is not specified in `UNICODE_SELECTED_MODES`, using their respective keycodes. @@ -151,7 +151,7 @@ If your keyboard has working EEPROM, it will remember the last used input mode a ### ** macOS ** -**Mode Name:** `UNICODE_MODE_MAC` +**Mode Name:** `UNICODE_MODE_MACOS` macOS has built-in support for Unicode input as its own input source. It supports all possible code points by way of surrogate pairs for code points above `U+FFFF`. -- cgit v1.2.3