Relax the requirements on addKeysym() so that it can add new
entries that still require modifying the current modifier state.


git-svn-id: https://tigervnc.svn.sourceforge.net/svnroot/tigervnc@5104 3789f03b-4d11-0410-bbf8-ca57d06f2519
Not sure what I was smoking when I wrote this. You need
to provide both pointers, even if you are just interested
in the upper case symbol.


git-svn-id: https://tigervnc.svn.sourceforge.net/svnroot/tigervnc@5105 3789f03b-4d11-0410-bbf8-ca57d06f2519
XkbTranslateKeyCode() is not implemented according to
specification in any system I can find, so change our code
to follow reality rather than specification.


git-svn-id: https://tigervnc.svn.sourceforge.net/svnroot/tigervnc@5106 3789f03b-4d11-0410-bbf8-ca57d06f2519
The cause of the keyboard mapping change is not a X11 request,
so don't pretend like it is.


git-svn-id: https://tigervnc.svn.sourceforge.net/svnroot/tigervnc@5107 3789f03b-4d11-0410-bbf8-ca57d06f2519
xkbcomp ignores keycodes without names, so make sure any keycode
we use actually has one.


git-svn-id: https://tigervnc.svn.sourceforge.net/svnroot/tigervnc@5108 3789f03b-4d11-0410-bbf8-ca57d06f2519
Adding normal alphabetic keysyms as ONE_LEVEL did not behave
correctly when CapsLock is active, so start using the ALPHABETIC
type for those instead.


git-svn-id: https://tigervnc.svn.sourceforge.net/svnroot/tigervnc@5109 3789f03b-4d11-0410-bbf8-ca57d06f2519
Copy 5104:5109 from trunk.


git-svn-id: https://tigervnc.svn.sourceforge.net/svnroot/tigervnc@5110 3789f03b-4d11-0410-bbf8-ca57d06f2519