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

Determining required dead keys #361

Open
johngebbie opened this issue Jul 7, 2023 · 2 comments
Open

Determining required dead keys #361

johngebbie opened this issue Jul 7, 2023 · 2 comments
Labels
compose Indicates a need for improvements or additions to Compose handling enhancement Indicates new feature requests tools: interactive

Comments

@johngebbie
Copy link

Hello, I'm not sure how to programatically determine the required dead keys for a keysym. For example, I don't know how you'd get that you need to type dead_circumflex and e to type ecircumflex in the fr layout.

how-to-type doesn't seem to implement it, with this outputting no entries:

xkbcli how-to-type --layout fr --keysym ecircumflex

I think ecircumflex could be found under a level with xkb_keymap_key_get_syms_by_level, but (if that's even right) I'm not sure how to map the levels to the required dead keys.

My end goal is to have my uinput tool support typing symbols that require dead keys.

@wismill wismill added compose Indicates a need for improvements or additions to Compose handling tools: interactive question Indicates that an issue, pull request, or discussion needs more information labels Jul 12, 2023
@wismill
Copy link
Member

wismill commented Jul 12, 2023

Currently the tool how-to-type does not support Compose. It means it will not look for keysyms that are the result of e.g. a sequence consisting of a dead key and a letter, such as: <dead_circumflex> <e>.

Unfortunately it does not seem there is a public API to get a sequence from its result.

@johngebbie
Copy link
Author

Thank you, it's good to know I'm not just not seeing it. Shall I make this a feature request?

@wismill wismill added enhancement Indicates new feature requests and removed question Indicates that an issue, pull request, or discussion needs more information labels Sep 20, 2023
@wismill wismill added this to the 1.7.0 milestone Sep 20, 2023
@wismill wismill removed this from the 1.7.0 milestone Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compose Indicates a need for improvements or additions to Compose handling enhancement Indicates new feature requests tools: interactive
Projects
None yet
Development

No branches or pull requests

2 participants