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

Support for different keyboard layouts #22

Open
FattusMannus opened this issue Oct 23, 2013 · 5 comments
Open

Support for different keyboard layouts #22

FattusMannus opened this issue Oct 23, 2013 · 5 comments

Comments

@FattusMannus
Copy link

I see that the library works very well when using US or UK keyboard layouts - Great Job.

However there are a few issues when using a French keyboard (the only non English language I have tried).
For example, on a french keyboard, to get numbers, you have to use shift where the symbols are non shifted. The library detects the opposite way (The same as in English based languages)

Also when pressing the symbol keys (the ones between alphabet and the enter key), the wrong symbol is detected.
Is this a limitation or is it technically possible to handle these cases?

@dmauro
Copy link
Owner

dmauro commented Oct 23, 2013

I honestly don't know if it's a solvable problem, but I would love to find out and make it easy for people to add support for different language keyboards.

@FattusMannus
Copy link
Author

I tried to implement my own keyboard system and your is miles better.
If you let me know what I can do to help, Ill do my best

@dmauro
Copy link
Owner

dmauro commented Oct 23, 2013

The top comment here is probably relevant to this conversation:
https://news.ycombinator.com/item?id=6464138

@drubb
Copy link

drubb commented Jul 25, 2016

What about supporting numerical keycodes? For example, on a german keyboard, the 'fence' character (#) has code 163. So if we could alternatively specify the code instead of the character in listener combos, it might help supporting some kind of internationalization.

@dmauro
Copy link
Owner

dmauro commented Jul 25, 2016

It's not so much an issue of how to map the different possible keyboards, but afaik there is no way to tell how a user's keyboard is mapped. Of course you could potentially offer the user a setting, that we could for sure build support for, but that's far from ideal I suppose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants