#631 Keyboard dead keys not working

[Anonymous]

It appears that TightVNC (Win32) is having problems
when the client computer (running the VNC viewer) is
using a keyboard layout that includes so-called "dead
keys". I use the keyboard layout "US International",
where pressing the ' (apostrophe) key is a dead key: it
does not do anything at first, but then typing e gives
é, or pressing Space gives the normal apostrophe.

In the current stable release 1.2.9 and all previous
versions, typing such a dead key in the viewer's
keyboard layout behaves as if it had been pressed twice
(so pressing ' yields two apostrophes).

In the current development version, 1.3-dev, the dead
keys are completely ignored unless I actually press
them twice in succession; pressing them once and then
either e or Space behaves as if I had only pressed e or
Space, respectively, without the dead key.

This bugreport may be related to this one:
http://sourceforge.net/tracker/index.php?func=detail&aid=1242907&group_id=14067&atid=114067
although I have not seen the other problem reported in
that one, that spurious characters appear when typing
fast. But then again, I'm not using the German keyboard
layout.

Dead keys are handled correctly if the server's layout
has them but the client layout doesn't.

[Nobody/Anonymous]

Logged In: NO

I am having the same problem. I use a US-International keyboard to type characters such as ü and Ä. Using the US-Int. keyboard, you do this by typing a double-quotation mark ("), then pressing u or shift-a (as in the examples). The quotation mark key does nothing at first. This user calls it the "dead key". In VNC, with US-Int keyboard on the client, it doesn't work whether or not I have US-Int. keyboard enabled on the server. But I suspect, since these bug reports are now verging on ancient, that nothing will be done to fix this. Too bad. I'll continue to use Tightvnc anyway. It's the fastest VNC I've found for my purposes.