en_GB.UTF-8 In vtm not working properly

[rasielab]

Using putty ssh mc show tui fine but when I try to open mc inside vtm the ui char are displayed wrong. In addition also windows icon are wron(minimize, close, etc...)

mc inside vtm

my locale

mc outside vtm

Linux raspberrypi105 6.6.74+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux

please do not hesitage if you need additional info

[o-sdn-o]

There seems to be some inconsistency with the code pages used. Vtm uses exclusively UTF-8 for its output, and perhaps Putty needs to be explicitly told to use UTF-8. I'll investigate this further. Thanks for the feedback.

[rasielab]

This is the way you explicitly indicate in putty to use UTF-8

[o-sdn-o]

This is the way you explicitly indicate in putty to use UTF-8

Does this setting fix the issue?

[o-sdn-o]

Off-topic question, have you tried connecting from a Windows host using the command vtm.exe ssh pi@raspberrypi105 vtm? When connected in this way (vtm ssh ... vtm), the vtm output is performed more efficiently directly without reencoding the text stream. Note that vtm does not have ssh built in, it uses system-wide ssh (ssh.exe, OpenSSH) to connect.

You could try to run vtm.exe ssh pi@raspberrypi105 vtm --run mc to get mc remotely in a standalone window. If you want to use plink.exe (a command-line interface to the PuTTY back ends) you can run vtm.exe --run dtvt plink.exe -pw _your_password_ pi@raspberrypi105 vtm

[rasielab]

• Remote character set on putty did no resolve the issue
• vtm.exe ssh pi@raspberrypi105 vtm --run mc
  
  -vtm.exe --run dtvt plink.exe -pw your_password pi@raspberrypi105 vtm
  

[o-sdn-o]

Wow, Interesting.

[rasielab]

I am using latest raspbian lite arm64 version, without any additional stuf installed. The fresh installation start having issues with native putt+mc connection by ssh but after the #711 (comment) config it was resolved. Now I am facing similar charset problem testing vtm

[o-sdn-o]

If this were a problem with the encoding, then it is not known how the character … (U+2026 Horizontal Ellipsis, UTF-8 Encoding: 0xE2 0x80 0xA6) slipped into the output.

Very interesting.

[o-sdn-o]

It's very similar to #681.

[o-sdn-o]

I tried to fix the text encoding in the v0.9.99.67 release. Could you please check it.

[rasielab]

Left side putty executing mc on a fresh raspbian arm64 install, on the right, putty and same configurations(Configuration/Window/Translation and Configuration/Connection/Data)

*you can see the vtm version number(latest)

[o-sdn-o]

ok. Thank you for testing. I'll keep digging further.

[o-sdn-o]

I got instant repro 😀

[o-sdn-o]

👌

[o-sdn-o]

I fix the text encoding in the v0.9.99.68 release. ARM architecture prefers unsigned char (0..255) in contrast to x86, where signed char (-128..127) is preferred.