First the good news: I believe VT100 does not produce garbage characters here. Unfortunately, I have to disappoint you from now on. The Tectia client currently still works only with one legacy Windows ANSI code page. I suppose in your case it is Windows-1252. So if you could set your remote Linux session to work in windows-1252 encoding all characters should show correctly. Also if you set the remote locale's charset some version of US-ASCII things should work fine. It is actually these 2 characters that show incorrectly:

from the UTF-8 encoded values and the Windows-1252 encoding you can understand why it shows the way it does. The Windows UI client does not contains means of conversions yet. One day it may. The command-line client sshg3 contains undocumented option for that. I talked about it here.

I believe problem #2 will be some variation of Problem #1. Let me know if you need more input.

We would desperately want to have proper Unicode support available in client and server on Windows, be most of the time we are forced to deal with "more urgent" issues.

BTW: The Linux/Unix version of Tectia SSH Client and Server should have no problems with UTF-8.

Thanks very much, Martin. By the way, these issues have existed since all the way back in your free SSH Secure Shell client from 2003. Hopefully you guys will have a break from the "more urgent" issues to implement this Unicode support sometime!