an error in keyboard layouts?

[tachyon]

Hi,
i had problems with ultravnc lastest version with sending /?;:+_- characters. I investigated the problem and found out that this problem is related to the keyboard layout. I'm from czech republic and i'm using czech programmers keyboard layout (the same as english but with alt gr there are special characters). These characters were not posted to some applications (like stardict and xchat (they use GTK) and console applications (like FAR). When i changed the keyboard layout everything worked suddenly ok. There are some data you may need to fix the problem (please note i'm not too much familiar with the ultravnc internal structure (mabye some technical documentation would be nice ?) so I may be completely wrong).

WinVnc.log (working machine)
Tue Oct 06 22:38:42 2009
keysym 0x2f SHORT s 191latin-1 key: keysym 47(0x2f) vkCode 0xbf down 1 capslockOn 0
keysym 0x2f SHORT s 191latin-1 key: keysym 47(0x2f) vkCode 0xbf down 0 capslockOn 0
keysym 0x2f SHORT s 191latin-1 key: keysym 47(0x2f) vkCode 0xbf down 1 capslockOn 0
keysym 0x2f SHORT s 191latin-1 key: keysym 47(0x2f) vkCode 0xbf down 0 capslockOn 0

WinVnc.log (Not working machine)
Tue Oct 06 22:41:40 2009
keysym 0x2f SHORT s 2011fake 17 down
fake 18 down
fake 16 down
latin-1 key: keysym 47(0x2f) vkCode 0xdb down 1 capslockOn 0
fake 16 up
fake 18 up
fake 17 up
keysym 0x2f SHORT s 2011latin-1 key: keysym 47(0x2f) vkCode 0xdb down 0 capslockOn 0
Tue Oct 06 22:41:41 2009
keysym 0x2f SHORT s 2011fake 17 down
fake 18 down
fake 16 down
latin-1 key: keysym 47(0x2f) vkCode 0xdb down 1 capslockOn 0
fake 16 up
fake 18 up
fake 17 up
keysym 0x2f SHORT s 2011latin-1 key: keysym 47(0x2f) vkCode 0xdb down 0 capslockOn 0
keysym 0x2f SHORT s 2011fake 17 down
fake 18 down
fake 16 down
latin-1 key: keysym 47(0x2f) vkCode 0xdb down 1 capslockOn 0
fake 16 up
fake 18 up
fake 17 up


The host keyboard layout if the machine is not working is 0xF00A0405 (it is the machine where is the server running)
The host keyboard layout if the machine is working is 0x04090409 (it is the machine where is the server running)

I suspect the problem is here
uvnc-source\winvnc\winvnc\vnckeymap.cpp

line 560
SHORT s = VkKeyScan(keysym);

I think that VkKeyScanEx should be used instead to determine the appropriate keyboard layout.

I hope that this is not in the known issues I wasn't able to find them anywhere.

[redge]

did you try to enable japanese keyboard on winvnc admin properties ?
is totally unrelated to japanese but international keyboard

enable japanese keyboard but need the same keyboard at both side.
cz <--> cz, should success
us <--> cz, fail