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

Non-US desktop PC #35

Closed
tschulte opened this issue Jan 30, 2014 · 2 comments
Closed

Non-US desktop PC #35

tschulte opened this issue Jan 30, 2014 · 2 comments

Comments

@tschulte
Copy link

Disclaimer: I was not able to test this, because I don't have my ErgoDox yet.

My plan is to connect my ErgoDox and another standard keyboard to my PC. The OS will be configured to use querz (German layout), because people coming to my desktop shall be able to type. The ErgoDox should allow me to type in my layout of choice (http://neo-layout.org).

If I understand correctly from inspecting the source code, there are some issues when the keyboard is connected to a PC using a non-US layout:

First of all, the neo layout does support some chars, that are not available on the standard querz keyboard. Therefore I would use the key_function type_string. This method tries to send key codes for all the chars available on a standard ansi keyboard. But that will result in wrong keycodes being send for these chars: "[Groovy, Baby]" with the keyboard attached to a German PC will send "üGroovz, Babz+". Workaround: Only use that method for chars that are not on a US keyboard.

Second: I need to define the layout using the US layout in mind, to get the correct char when pressing a particular key. E.g. when pressing the key where there would be a "z" on a German keyboard ("y" on a US keyboard), I really want it to be an "ü". To get an "ü" when the OS thinks the keyboard uses the German layout, it has to send the keycode for "[" on a US keyboard.

It should be easy to define the desired outcome without having to think in respect to the US layout. There should be some #define statement to set the target language code, and then I want to be able to just type what each key should produce.

@jave
Copy link

jave commented Jan 30, 2014

see my comment for #36

@benblazak
Copy link
Owner

Not entirely sure what the issue is... I hope you'll forgive me for not being able to read carefully and respond thoroughly, as school just started, and I'm super busy. See my comment for #36 too though. I have a feeling the two issues are caused by the same thing (i.e. the USB HID standard for boot keyboards).

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

3 participants