diff options
author | Ryan <fauxpark@gmail.com> | 2020-02-25 12:54:51 +1100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-02-25 12:54:51 +1100 |
commit | bb8d4b4d23ee04f6034f8880b8a9f93fa4673c38 (patch) | |
tree | 369bef3cc7ed134775fe25ef81948289023779ec /docs/feature_unicode.md | |
parent | 93c5307fd60c35780921570ccf41a1806847eb9c (diff) | |
download | qmk_firmware-bb8d4b4d23ee04f6034f8880b8a9f93fa4673c38.tar.gz |
`send_unicode_string()`: Add support for code points > 0xFFFF (#8236)
Diffstat (limited to 'docs/feature_unicode.md')
-rw-r--r-- | docs/feature_unicode.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/feature_unicode.md b/docs/feature_unicode.md index 546af2521..697541458 100644 --- a/docs/feature_unicode.md +++ b/docs/feature_unicode.md @@ -195,7 +195,7 @@ By default, when the keyboard boots, it will initialize the input mode to the la ## `send_unicode_string()` -This function is much like `send_string()` but allows you to input UTF-8 characters directly, currently up to code point U+FFFF. Make sure your `keymap.c` is formatted in UTF-8 encoding. +This function is much like `send_string()` but allows you to input UTF-8 characters directly, and supports all code points (provided the selected input method also supports it). Make sure your `keymap.c` is formatted in UTF-8 encoding. ```c send_unicode_string("(ノಠ痊ಠ)ノ彡┻━┻"); @@ -210,7 +210,6 @@ send_unicode_hex_string("0028 30CE 0CA0 75CA 0CA0 0029 30CE 5F61 253B 2501 253B" ``` An easy way to convert your Unicode string to this format is by using [this site](https://r12a.github.io/app-conversion/), and taking the result in the "Hex/UTF-32" section. -Unlike `send_unicode_string()` this function supports code points up to U+10FFFF. ## Additional Language Support |