-
Notifications
You must be signed in to change notification settings - Fork 33
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
(KEYBOARD-LAYOUT) DingusPPC can't write semicolon, colon, etc. when the host machine is in Spanish locale. #109
Comments
Someone independently reported a similar issue with the Italian keyboard. I'll have to see what's causing the characters to not be input. Also, if you have a log file, search for "Unknown key" for any discrepancies. Right now, international keyboard support is very much unpolished. |
ñ and Ñ keys are shown as Colon and Semicolon are wrongly written as "<" and ">". This "<" and that ">" are written as "," and "<" The accent "´" key is: The "·" is written as "ú". ¡ and ¿ Buttons are written as: ` and ^ keys are written as: This ç and Ç are written as: The \ button is written as: I would say, a long etc. So seems to be some missing keys in the map or barely understood by the SDL side. As you can see, this make the thing to be barely impossible to develop or to input simple directories. |
It'll be better to use a keycode file in the future. This will hopefully do for now.
Thanks for your fast commit. :D At least, the half of the keys now are doing what they are supposed to. |
Describe the bug
DingusPPC can't write semicolon, colon, etc. when the host machine is in Spanish locale. I guess that is happening with multiple layouts, not only Spanish, but the only one I tested is that one.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should write the correct layout.
Screenshots
If applicable, add screenshots to help explain your problem.
Device Information (please complete the following information):
Additional context
I am doing tests for the WIN NT for PowerPC macs. Anyway, I can test other machines if you want to, but ask me what to test or to do, since I am not "Mac user".
The text was updated successfully, but these errors were encountered: