diff options
author | cbbrowne <cbbrowne@cbbrowne.tor.int-afilias.info> | 2016-10-26 16:55:41 +0200 |
---|---|---|
committer | cbbrowne <cbbrowne@cbbrowne.tor.int-afilias.info> | 2016-10-26 16:55:41 +0200 |
commit | 2a2920d92c5c314fe6291c92dee92fb6ff8294fe (patch) | |
tree | a8cc9ba8791d01c8bb5668ffd46508dd594c5aeb /readme.md | |
parent | 6a0313ac262af5d717a33a0b01bd44c9e38362f3 (diff) | |
parent | f44ead146214381aa78344f1d4fe3e1b24010c95 (diff) | |
download | qmk_firmware-2a2920d92c5c314fe6291c92dee92fb6ff8294fe.tar.gz qmk_firmware-2a2920d92c5c314fe6291c92dee92fb6ff8294fe.tar.xz |
Merge branch 'master' of https://github.com/jackhumbert/qmk_firmware
Diffstat (limited to 'readme.md')
-rw-r--r-- | readme.md | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -326,8 +326,14 @@ This allows you to send unicode symbols via `UC(<unicode>)` in your keymap. Only `UNICODEMAP_ENABLE` This allows sending unicode symbols using `X(<unicode>)` in your keymap. Codes -up to 0xFFFFF are supported, including emojis. But you need to maintain a -separate mapping table in your keymap file. +up to 0xFFFFFFFF are supported, including emojis. You will need to maintain +a separate mapping table in your keymap file. + +Known limitations: +- Under Mac OS, only codes up to 0xFFFF are supported. +- Under Linux ibus, only codes up to 0xFFFFF are supported (but anything important is still under this limit for now). + +Characters out of range supported by the OS will be ignored. `BLUETOOTH_ENABLE` |