X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=docs%2Funicode.md;h=2dfb38d96ad8dbb4e15908b816c04ce025a77123;hb=c02de0932ad9a546727bd7097ba33c5b17aebd98;hp=ae722fe2b467ba24a1df4a0112c9bdf8de5e6e6a;hpb=c33434c0d64dd7cbd5f6371c7cb4ac5e05924944;p=qmk_firmware.git

diff --git a/docs/unicode.md b/docs/unicode.md
index ae722fe2b..2dfb38d96 100644
--- a/docs/unicode.md
+++ b/docs/unicode.md
@@ -24,6 +24,7 @@ sort of like macro. Unfortunately, each OS has different ideas on how Unicode is
 This is the current list of Unicode input method in QMK:
 
 * UC_OSX: MacOS Unicode Hex Input support. Works only up to 0xFFFF. Disabled by default. To enable: go to System Preferences -> Keyboard -> Input Sources, and enable Unicode Hex.
+* UC_OSX_RALT: Same as UC_OSX, but sends the Rigt Alt key for unicode input
 * UC_LNX: Unicode input method under Linux. Works up to 0xFFFFF. Should work almost anywhere on ibus enabled distros. Without ibus, this works under GTK apps, but rarely anywhere else.
 * 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.
 * UC_WINC: Windows Unicode input using WinCompose. Requires [WinCompose](https://github.com/samhocevar/wincompose). Works reliably under many (all?) variations of Windows.