Clipboard does not transfer unicode strings between client and server

[Soukyuu]

I'm using tigervnc 1.3.1 as server on arch linux x64 and ultravnc as client on windows 8.1 x64. When copying a Japanese string between the server and a client, the clipboard contents are not copied as unicode but ansi with a wrong codepage.

For example, copying "テスト" results in "???". It doesn't matter which way the copy&paste operation goes or which application is involved.

The server is configured to be able to display Japanese fonts, so it's not a font problem. I can also copy&paste between the applications running in the vnc session, it only breaks when I try to transfer text between the server and client...

UltraVNC apparently supports unicode (scroll down to the notes section), and I don't see why tigervnc should be unable to do it.

I have made a thread on arch forums first and was advised to post here as it doesn't seem to be an Arch specific bug/configuration issue.

[CendioOssman]

This is a limitation of VNC's clipboard protocol. UltraVNC has made some extensions to it, but they are currently not documented and no one has yet to look at porting it over to TigerVNC.

[bphinz]

The java client should encode & decode clipboard data as UTF-8 byte streams. I'd be interested to know if/how well it handles something like Japanese if you have the time to test it. Thanks.

[CendioOssman]

I don't think that's really a good idea as it violates the protocol and might not do the right thing. Unless you are using an extension and not the standard clipboard stuff?

[bphinz]

On Thu, Feb 26, 2015 at 6:58 AM, Pierre Ossman (Work account) <
notifications@github.com> wrote:

I don't think that's really a good idea as it violates the protocol and
might not do the right thing. Unless you are using an extension and not the
standard clipboard stuff?

Ugh! You're right. I don't know how I managed to miss it, but the spec
does say that only ISO8859-1 is supported.

[changkun]

Anybody fixed this notourbug until now?

[dbedrenko]

Would be really great to have this extension in TigerVNC; it's a big limitation. It's the only reason why I don't use TigerVNC, and have to rely on otherwise inferior software like rdesktop and x2go.

[CendioOssman]

I have a branch for this here:

https://github.com/CendioOssman/tigervnc/tree/clipboard

I haven't had time to finish it up though, but people are free to test it out.

[Arminmsg]

Are there any updates on this issue, I assume there is still no unicode support for clipboard?

[CendioOssman]

Actually, PR #834 will fix this. A review and/or testing would be nice for those who can. :)

[jetaimy]

我用Windows10 vncviewer7.8连接服务器centos 7.9上的tigervnc-1.13.0进行通信，两边中文都可以正常显示，但无论复制粘贴中文总是乱码，和没升级之前一样的utf乱码，解决方案如下：
1、首先在服务器centos 7.9上的tigervnc-1.8.0升级到了tigervnc-1.13.0：
[admin@$ sudo yum localinstall tigervnc-server-1.13.1-1.el7.x86_64.rpm tigervnc-server-module-1.13.1-1.el7.x86_64.rpm tigervnc-server-minimal-1.13.1-1.el7.x86_64.rpm tigervnc-license-1.13.1-1.el7.noarch.rpm tigervnc-selinux-1.13.1-1.el7.noarch.rpm
2、其次将客户端从vncviewer换成tiger vncviewer-1.13.1就好了

I use Windows10 vncviewer7.8 to connect tigervnc-1.13.0 on the server centos 7.9 for communication, both sides of the Chinese can be displayed normally, but no matter the copy and paste Chinese is always garbled, and the same utf garbled before the upgrade, the solution is as follows:

1. First upgrade tigervnc-1.8.0 on centos 7.9 to tigervnc-1.13.0:
   [admin@$sudo yum localinstall tigervc-server-1.13.1-1.el7.x86_64. rpm tigervc-server-module-1.13.1-1.el7.x86_64. rpm Tigervc-server-minimal-1.13.1-1.el7.x86_64. rpm Tigervc-license-1.13.1-1.el7.noarch.rpm Tigervnc - selinux - 1.13.1-1. El7. Noarch. RPM

2, then change the client from vncviewer to tiger vncviewer-1.13.1

[jetaimy]

我用Windows10 vncviewer7.8连接服务器centos 7.9上的tigervnc-1.8.0进行通信，两边中文都可以正常显示，但无论复制粘贴中文总是乱码，和没升级之前一样的utf乱码，解决方案如下： 1、首先在服务器centos 7.9上的tigervnc-1.8.0升级到了tigervnc-1.13.0： [admin@$ sudo yum localinstall tigervnc-server-1.13.1-1.el7.x86_64.rpm tigervnc-server-module-1.13.1-1.el7.x86_64.rpm tigervnc-server-minimal-1.13.1-1.el7.x86_64.rpm tigervnc-license-1.13.1-1.el7.noarch.rpm tigervnc-selinux-1.13.1-1.el7.noarch.rpm 2、其次将客户端从vncviewer换成tiger vncviewer-1.13.1就好了，tightvnc-2.8.81-gpl-setup-64bit客户端也还是乱码

I use Windows10 vncviewer7.8 to connect tigervnc-1.8.0 on the server centos 7.9 for communication, both sides of the Chinese can be displayed normally, but no matter the copy and paste Chinese is always garbled, and the same utf garbled before the upgrade, the solution is as follows:

1. First upgrade tigervnc-1.8.0 on centos 7.9 to tigervnc-1.13.0:
   [admin@$sudo yum localinstall tigervc-server-1.13.1-1.el7.x86_64. rpm tigervc-server-module-1.13.1-1.el7.x86_64. rpm Tigervc-server-minimal-1.13.1-1.el7.x86_64. rpm Tigervc-license-1.13.1-1.el7.noarch.rpm Tigervnc - selinux - 1.13.1-1. El7. Noarch. RPM

2, then change the client from vncviewer to tiger vncviewer-1.13.1

[class-undefined]

我用Windows10 vncviewer7.8连接服务器centos 7.9上的tigervnc-1.13.0进行通信，两边中文都可以正常显示，但无论复制粘贴中文总是乱码，和没升级之前一样的utf乱码，解决方案如下： 1、首先在服务器centos 7.9上的tigervnc-1.8.0升级到了tigervnc-1.13.0： [admin@$ sudo yum localinstall tigervnc-server-1.13.1-1.el7.x86_64.rpm tigervnc-server-module-1.13.1-1.el7.x86_64.rpm tigervnc-server-minimal-1.13.1-1.el7.x86_64.rpm tigervnc-license-1.13.1-1.el7.noarch.rpm tigervnc-selinux-1.13.1-1.el7.noarch.rpm 2、其次将客户端从vncviewer换成tiger vncviewer-1.13.1就好了

I use Windows10 vncviewer7.8 to connect tigervnc-1.13.0 on the server centos 7.9 for communication, both sides of the Chinese can be displayed normally, but no matter the copy and paste Chinese is always garbled, and the same utf garbled before the upgrade, the solution is as follows:

1. First upgrade tigervnc-1.8.0 on centos 7.9 to tigervnc-1.13.0:
   [admin@$sudo yum localinstall tigervc-server-1.13.1-1.el7.x86_64. rpm tigervc-server-module-1.13.1-1.el7.x86_64. rpm Tigervc-server-minimal-1.13.1-1.el7.x86_64. rpm Tigervc-license-1.13.1-1.el7.noarch.rpm Tigervnc - selinux - 1.13.1-1. El7. Noarch. RPM

2, then change the client from vncviewer to tiger vncviewer-1.13.1

非常感谢，在我的机器上成功了！