-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have realised that the tables main_key_scan_abnt_qwerty and main_key_vkey_abnt_qwerty are both wrong. But one error compensates the other. For example, when I press x the message "Translating key VK_Z..." is displayed and an 'x' appears on the screen. The other problem with the abnt2 keyboard is that wine assumes that: /* Only the Keypad keys 0-9 and . send different keysyms * depending on the NumLock state */
This is not true for the abnt2 keyboard. The comma may also work as a delete. The attached patch solves both problems. I have tested the patch with a abnt2 and a us-int keyboard. Both work correctly. One last comment: as far as I know, all abnt2 keyboards have an "alt gr" key. How may I contact Mauro Carvalho Chehab and Raul Gomes Fernandes? Thanks Rafael Ávila de Espíndola -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAdrYZLlrfGJ8JUHwRAkxbAKCdrcsZ52jBWNtGqggmEzCKevhCgwCfclmx 0uNw50qMBFAp5HzZdIBtCjY= =NdP/ -----END PGP SIGNATURE-----
Index: dlls/x11drv/keyboard.c =================================================================== RCS file: /home/wine/wine/dlls/x11drv/keyboard.c,v retrieving revision 1.50 diff -r1.50 keyboard.c 91,92c91,92 < /* \ z x c v b n m , . / */ < 0x5e,0x2C,0x2D,0x2E,0x2F,0x30,0x31,0x32,0x33,0x34,0x35, --- > /* z x c v b n m , . ; / */ > 0x2C,0x2D,0x2E,0x2F,0x30,0x31,0x32,0x33,0x34,0x35,0x59, 154c154 < VK_OEM_7,VK_Z,VK_X,VK_C,VK_V,VK_B,VK_N,VK_M,VK_OEM_COMMA,VK_OEM_PERIOD,VK_OEM_2, --- > VK_Z,VK_X,VK_C,VK_V,VK_B,VK_N,VK_M,VK_OEM_COMMA,VK_OEM_PERIOD,VK_OEM_2,VK_OEM_7, 851c851 < 0, 0, 0, 0, 0, 0, 0, 0, /* FF28 */ --- > 0, 0, 0, 0, VK_OEM_COMMA, 0, 0, 0, /* FF28 */ 948c948 < if ((keysym >= 0xFFAE) && (keysym <= 0xFFB9) && (keysym != 0xFFAF) --- > if ((((keysym >= 0xFFAE) && (keysym <= 0xFFB9) && (keysym != 0xFFAF)) || (keysym == 0x2C)) 950c950 < /* Only the Keypad keys 0-9 and . send different keysyms --- > /* Only the Keypad keys 0-9, . and , (in the abnt2 keyboard) send different keysyms
