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

some international characters seem not to be available via compose mechanism #8

Open
vlnn opened this issue Jan 11, 2023 · 3 comments

Comments

@vlnn
Copy link
Contributor

vlnn commented Jan 11, 2023

I'm trying to create a full layout of Ukrainian characters, creating ukrainian.dtsi similar to the ones in this repo (should be available https://github.com/vlnn/samoklava-zmk-config/blob/test-zmk-nodefree-config/zmk-nodefree-config/international_chars/ukrainian.dtsi). It mostly works -- except several, well, exceptions:

ZMK_UNICODE_PAIR(ua_a, N0, N4, N3, N0, N0, N4, N1, N0) // а/А
and
ZMK_UNICODE_PAIR(ua_r, N0, N4, N4, N0, N0, N4, N2, N0) // р/Р

They are just ignored on my MacBook. Any hints/ideas/proposals on how to work this through/around?

@vlnn
Copy link
Contributor Author

vlnn commented Jan 11, 2023

OK, it's a known bug in macos https://discussions.apple.com/thread/253636848 . Still infuriating -- and perhaps should be mentioned in documentation (e.g. highly demanded

ZMK_UNICODE_PAIR(fr_a_grave, N0, N0, E, N0, N0, N0, C, N0) // à/À

will not work on macos devices).

Ideas for the workarounds are welcome.

@urob
Copy link
Owner

urob commented Jan 12, 2023

It sounds like this is clearly a bug on the macOS side. While very unfortunate I'm not sure if there's something that can be down from the ZMK side. Maybe there's a 3rd party tool like there is WinCompose for Windows that could be used to handle the Unicode reception instead?

Edit: regarding the two letters that aren't working, could you for now replace them with a latin A and P?

@vlnn
Copy link
Contributor Author

vlnn commented Jan 12, 2023

I agree it's not ZMK or zmk-nodefree-config fault. I'll investigate and will update if I get to some level of resolution.

The problem with using latin chars A and P is that searching, autocompletion and dictionaries will be all broken -- not something I can live with!

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