[PATCH 2/4] user32/tests: Do not expect char vkey to return the same char everywhere.

[Marvin]

Hi,

While running your changed tests, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?

Full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=58281

Your paranoid android.


=== w8adm (32 bit report) ===

user32:
input.c:2138: Test failed: expected WM_LBUTTONDOWN message
input.c:2139: Test failed: expected WM_LBUTTONUP message
input.c:2166: Test failed: expected WM_NCHITTEST message
input.c:2167: Test failed: expected WM_RBUTTONDOWN message
input.c:2168: Test failed: expected WM_RBUTTONUP message
input.c:2196: Test failed: expected WM_NCHITTEST message
input.c:2197: Test failed: expected WM_LBUTTONDOWN message
input.c:2198: Test failed: expected WM_LBUTTONUP message
input.c:2224: Test failed: expected WM_NCHITTEST message
input.c:2251: Test failed: expected loop with WM_NCHITTEST messages
input.c:2304: Test failed: expected WM_LBUTTONDOWN message
input.c:2305: Test failed: expected WM_LBUTTONUP message

=== w1064v1809_ar (32 bit report) ===

user32:
input.c:1899: Test failed: ToAscii for character 'A' was 212 (expected 97)

=== w1064v1809_he (32 bit report) ===

user32:
input.c:1899: Test failed: ToAscii for character 'A' was 249 (expected 97)

=== w1064v1809_zh_CN (32 bit report) ===

user32:
input.c:261: Test failed: 2/0: wrong message 100/000000e5/002d0001 expected WM_KEYDOWN/00000058/002d0001
input.c:261: Test failed: 2/1: wrong message 104/000000e5/20380001 expected WM_SYSKEYDOWN/00000012/20380001
input.c:261: Test failed: 2/2: wrong message 105/000000e5/c0380001 expected WM_SYSKEYUP/00000012/c0380001
input.c:261: Test failed: 2/3: wrong message 101/00000058/802d0001 expected WM_KEYUP/00000058/c02d0001
input.c:261: Test failed: 3/0: wrong message 100/000000e5/002d0001 expected WM_KEYDOWN/00000058/002d0001
input.c:261: Test failed: 3/1: wrong message 104/000000e5/20380001 expected WM_SYSKEYDOWN/00000012/20380001
input.c:261: Test failed: 3/3: wrong message 101/000000e5/c0380001 expected WM_KEYUP/00000012/c0380001
input.c:261: Test failed: 4/0: wrong message 104/000000e5/20380001 expected WM_SYSKEYDOWN/00000012/20380001
input.c:261: Test failed: 4/3: wrong message 101/000000e5/c0380001 expected WM_KEYUP/00000012/c0380001
input.c:261: Test failed: 5/0: wrong message 104/000000e5/20380001 expected WM_SYSKEYDOWN/00000012/20380001
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:1155: Test failed: Unexpected vkCode 0xa2, expected 0.
input.c:2752: Test failed: 0: wrong originId 4
input.c:2752: Test failed: 0: wrong originId 4