> That's fair. I spoke with a counterpart of mine in Denmark, and he thinks
> he's found the parts of the code that do this, and he's trying to at least
> get support for ^ and ~ characters. If we get that done, we'll submit it
> to you.
Great, thanks. There is almost certainly some simple basic issue behind the
dead-key problems, so that once one works, they all should. Bear in mind
that the keyboard model used by VNC is that the *client* should handle all
unusual keyboard combinations and that the server should accept all incoming
symbols and make sure they get to the applications intact.
I think Xvnc is probably complete in this respect but I suspect that the
Windows Viewer and Server are both broken to some extent.
Cheers & good luck!
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
