Fixing clipboard charset bug

[C3PO]

There is a problem with clipboard when you're connecting to UTF8 Linux VNC server from Windows CP1251 client. If you copy native UTF8 text from server you have gibberish on client and vice versa. The problem is that you can't read default system encoding UTF8 on windows and at the same you can't read default system encoding of Windows CP1251 client on linux with default UTF8 encoding.

Only latin is copied correctly (by apparent reasons).

I suggest you to add an option or feature which would allow clipboard re-encoding on fly.

I.e.

Client: Windows with default CP1251 system encoding connecting to Server with default UTF8 system encoding

Copy from server to client - before pushing to windows clipboard the text is converted to CP1251 on fly, transparently

Copy from client to server - CP1251 client clipboard encoding is converted to UTF8 and then pushed to the server clipboard.

I checked out 4 VNC clinets - XRDP, RealVNC, UltaVNC, Thigh VNC and by reason unknown this feature is not implemented in any of the viewers. That means that Clipboard is only operational when both client and server have the same system default charset. I think that shortcoming might be classified as a bug.

I don't think there is any problem with iconv out there.

[B]

For those, like me, who have no idea what CP1251 is, Wikipedia says:

Windows-1251 (a.k.a. code page CP1251) is a popular 8-bit character encoding, designed to cover languages that use the Cyrillic alphabet such as Russian, Bulgarian, Serbian Cyrillic and other languages. It is the most widely used for encoding the Bulgarian, Serbian and Macedonian languages.

In modern applications, Unicode is a preferred character set.

Windows-1251 and KOI8-R (or its Ukrainian variant KOI8-U) are much more commonly used than ISO 8859-5, which never really caught on. In the future, both may eventually give way to Unicode.