diff options
author | skullY <skullydazed@gmail.com> | 2017-07-03 12:29:04 -0700 |
---|---|---|
committer | skullY <skullydazed@gmail.com> | 2017-07-03 12:29:04 -0700 |
commit | 2abff258b146a28a3411dbcc0d312061cd4bd5db (patch) | |
tree | 8ce21d6c1b9aa4596884c1e04a1b68ecbbddf500 | |
parent | 0ded95b88882ba7bdc1890f7462f0af96b10fadb (diff) | |
download | qmk_firmware-2abff258b146a28a3411dbcc0d312061cd4bd5db.tar.gz qmk_firmware-2abff258b146a28a3411dbcc0d312061cd4bd5db.zip |
Adjust headings on unicode
-rw-r--r-- | docs/unicode_and_additional_language_support.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/unicode_and_additional_language_support.md b/docs/unicode_and_additional_language_support.md index 562dae4b5..ae722fe2b 100644 --- a/docs/unicode_and_additional_language_support.md +++ b/docs/unicode_and_additional_language_support.md | |||
@@ -1,20 +1,20 @@ | |||
1 | ## Unicode support | 1 | # Unicode support |
2 | 2 | ||
3 | There are three Unicode keymap definition method available in QMK: | 3 | There are three Unicode keymap definition method available in QMK: |
4 | 4 | ||
5 | ### UNICODE_ENABLE | 5 | ## UNICODE_ENABLE |
6 | 6 | ||
7 | Supports Unicode input up to 0xFFFF. The keycode function is `UC(n)` in | 7 | Supports Unicode input up to 0xFFFF. The keycode function is `UC(n)` in |
8 | keymap file, where *n* is a 4 digit hexadecimal. | 8 | keymap file, where *n* is a 4 digit hexadecimal. |
9 | 9 | ||
10 | ### UNICODEMAP_ENABLE | 10 | ## UNICODEMAP_ENABLE |
11 | 11 | ||
12 | Supports Unicode up to 0xFFFFFFFF. You need to maintain a separate mapping | 12 | Supports Unicode up to 0xFFFFFFFF. You need to maintain a separate mapping |
13 | table `const uint32_t PROGMEM unicode_map[] = {...}` in your keymap file. | 13 | table `const uint32_t PROGMEM unicode_map[] = {...}` in your keymap file. |
14 | The keycode function is `X(n)` where *n* is the array index of the mapping | 14 | The keycode function is `X(n)` where *n* is the array index of the mapping |
15 | table. | 15 | table. |
16 | 16 | ||
17 | ### UCIS_ENABLE | 17 | ## UCIS_ENABLE |
18 | 18 | ||
19 | TBD | 19 | TBD |
20 | 20 | ||
@@ -28,11 +28,11 @@ This is the current list of Unicode input method in QMK: | |||
28 | * UC_WIN: (not recommended) Windows built-in Unicode input. To enable: create registry key under `HKEY_CURRENT_USER\Control Panel\Input Method\EnableHexNumpad` of type `REG_SZ` called `EnableHexNumpad`, set its value to 1, and reboot. This method is not recommended because of reliability and compatibility issue, use WinCompose method below instead. | 28 | * UC_WIN: (not recommended) Windows built-in Unicode input. To enable: create registry key under `HKEY_CURRENT_USER\Control Panel\Input Method\EnableHexNumpad` of type `REG_SZ` called `EnableHexNumpad`, set its value to 1, and reboot. This method is not recommended because of reliability and compatibility issue, use WinCompose method below instead. |
29 | * UC_WINC: Windows Unicode input using WinCompose. Requires [WinCompose](https://github.com/samhocevar/wincompose). Works reliably under many (all?) variations of Windows. | 29 | * UC_WINC: Windows Unicode input using WinCompose. Requires [WinCompose](https://github.com/samhocevar/wincompose). Works reliably under many (all?) variations of Windows. |
30 | 30 | ||
31 | ## Additional language support | 31 | # Additional language support |
32 | 32 | ||
33 | In `quantum/keymap_extras/`, you'll see various language files - these work the same way as the alternative layout ones do. Most are defined by their two letter country/language code followed by an underscore and a 4-letter abbreviation of its name. `FR_UGRV` which will result in a `ù` when using a software-implemented AZERTY layout. It's currently difficult to send such characters in just the firmware. | 33 | In `quantum/keymap_extras/`, you'll see various language files - these work the same way as the alternative layout ones do. Most are defined by their two letter country/language code followed by an underscore and a 4-letter abbreviation of its name. `FR_UGRV` which will result in a `ù` when using a software-implemented AZERTY layout. It's currently difficult to send such characters in just the firmware. |
34 | 34 | ||
35 | ## International Characters on Windows | 35 | # International Characters on Windows |
36 | 36 | ||
37 | [AutoHotkey](https://autohotkey.com) allows Windows users to create custom hotkeys among others. | 37 | [AutoHotkey](https://autohotkey.com) allows Windows users to create custom hotkeys among others. |
38 | 38 | ||