It's a better match for what the key symbolises, even though it is not
as common on Unix systems. But we want to avoid getting in to tailoring
things for any one specific input method implementation.

We don't know the size of the output buffer here and giving the input
string size is just confusing and upsets the compiler in some cases.

This is what display managers do, so it is expected by many
environments.

We terminated the child instead of the parent after fork().

Reported by Jan Grulich from Red Hat.

Windows either completely omits WM_KEYUP for these, or only sends it
just before the next WM_KEYDOWN for the key.

This covers some Alt+key presses as well.

Some of the virtual key codes for Japanese keys are used for other
things on other layouts, so we need to make sure we only use this look
up table when the layout is indeed set to Japanese.

This was already handled for most exit conditions, but not the early
ones.

Mainly fixes for Japanese and Korean keyboard layouts.

Added vkey mappings for Japanese keyboards because the special keys for Japanese input do not work on TigerVNC currently.

Not sure how this has changed, but ImageMagick is now using the first
-size to also determine how to scale the SVGs, which is not what we
want.

Anything else is excessive.

Added OS X JIS Keyboard keys (kVK_JIS_Eisu, kvK_JIS_Kana). The Kana and Eisu keys are used to alter IME behavior, but currently the Kana key produces an unwanted space character and the Eisu key does not work.

Each character is more than one byte, so adjust the clearing of the
buffer to reflect that.

Some code points are reserved for the UTF-16 coding itself and must not
appear as input data to the algorithm.

Signed bug prevented anything not ASCII from being coded correctly.

Everything outside of BMP was handled incorrectly and was coded as
completely different code points.

This would mess up most conversions from UTF-8 as the caller wouldn't
know how far to step to get to the next valid character, resulting in
markers for invalid data to be injected here and there.

Also add some unit tests to avoid this reoccurring.

It is now dynamically generated, so it will be in the build directory
and not in the source directory.

This is needed by vncserver which doesn't know which parameters are
boolean, and it cannot use the -Param=Value form as that isn't tolerated
by the Xorg code.

Refer @CMAKE_INSTALL_FULL_SYSCONF@ instead.

Like the native viewer, the Java viewer didn't store certificate
exceptions properly. Whilst not as bad as the native viewer, it still
failed to check that a stored certificate wouldn't be maliciously used
for another server. In practice this can in most cases be used to
impersonate another server.

Handle this like the native viewer by storing exceptions for a specific
hostname/certificate combination.

Not sure why this got in there, but it is incorrect as it results in
creating files with too liberal permissions.

Update Surface_X11.cxx

Runtime sellection of ARGB  XImage byte order

For some reason it got generated at an incorrect 20x20 size last time.

It should be using the safe wrappers for everything so make sure it
cannot bypass those and call the SConnection methods directly.

We incorrectly called the underlying functions instead of the safe
wrappers for the new clipboard functions. This had the effect of a)
crashing the entire server if one of these functions failed, and b) not
respecting the settings disabling the clipboard.