Skip to content
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

Unicode input that starts with a valid sequence can conflict with built-in sequences #323

Open
bigyihsuan opened this issue Jan 31, 2020 · 1 comment

Comments

@bigyihsuan
Copy link

I am trying to type Ɬ Latin Capital letter L With Belt (U+A7AD), which does not have a sequence by default.

I do Composeua7ad and expect but instead get ă7ad.

However, I can do Compose263aEnter for ☺ Smiling Face but not Composeua4d8 for ꓘ Lisu Letter Kha and instead get ă4d8.

In addition, I can do Composeuf9d1 for 六 CKJ Compatibility Ideograph U+F9D1.

Note that Composeuf is not a built-in sequence, but Composeua is for ă.

@sunaku
Copy link

sunaku commented Mar 6, 2024

@frankbenoit found a great workaround for this problem: insert an extra 0 zero in between the u and the actual hexcode:

  • Compose u 0 a 7 a d

In general, this approach seems to work for hexcodes (everything after the u) up to 6 digits long after the 0 zero insertion:

  • Compose u 1 F 5 2 5 → 🔥
  • Compose u 0 1 F 5 2 5 → 🔥
  • Compose u 0 0 1 F 5 2 5 → u001f525

sunaku added a commit to sunaku/glove80-keymaps that referenced this issue Mar 6, 2024
Thanks to @frankbenoit for finding this workaround:
samhocevar/wincompose#323

This fixes the ability to type "¡" using WinCompose, which would
previously emit "ă1\n" for that character key on the World layer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants