-
-
Notifications
You must be signed in to change notification settings - Fork 39.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange behaviour of Unicode function. #450
Comments
What OS are you using? Different operating systems have different unicode input methods, and maybe the default of QMK (osx, I think?) is not suitable for you. |
I use OSX 10.11.5. |
What happens when you press left alt, then, while held, 00FC, and release alt too? Does that input the correct character, or does ti do the |
Are you using the Unicode Hex Input? Keyboard > Input Sources > Other (at the bottom) > Unicode Hex Input. |
No I didn't. I was using US layout. Now I works just fine. Thanks. |
- issue qmk#450 - manipulating model causes the vuex model to ddos itself trying to manipulate arbitrarily high layer values.
* Add Vial-enabled default map to budget96 * Update rules.mk via suggestion Co-authored-by: Less/Rikki <86894501+lesshonor@users.noreply.github.com> * Suggestions to keymap.c Co-authored-by: Less/Rikki <86894501+lesshonor@users.noreply.github.com> --------- Co-authored-by: Less/Rikki <86894501+lesshonor@users.noreply.github.com>
I tried to implement a third layer which enables me to write German umlauts (äöü) and ß, while staying in US key layout. I didn't find another solution to this then mapping the keys in that layer to the corresponding unicode, but the behavior I got was very strange.
If I hit the key that I mapped to
UC(0x00FC)
, which should beü
according to Wikipedia I get the following:ººƒç
The text was updated successfully, but these errors were encountered: