Total Commander

2white
He reads with bugs. Was abcd, shows a. It was абвг, shows this.

2Fla$her
If you want to keep multilanguage comments, you should use only one of Unicode encodings - either UTF-8 or UTF-16. Otherwise some comments won't be displayed properly.

2Usher
I've previously tried with UTF-8. The result is the same.

2Fla$her
I use Windows-1250 (Polish) codepage and I don't have problems with Russian/Ukrainian both in filenames and in comments for both UTF-8 or UTF-16 encodings. Note that there should be only Unicode allowed, anything mixed with plain text or DOS charset may fail. See proper settings below:

Preferred type [Unicode UTF8  ] ☐ DOS charset
or
Preferred type [Unicode UTF16 ] ☐ DOS charset

There may be problems with already existing comments - in the worst case they should be converted manually.
What fonts do you use in TC?

Also: http://ppro.totalcmd.net/Scripts/EditFileComments.htm

2Usher
What difference does it make what fonts I use if the problem is precisely in calling the comment edit dialog from the attributes dialog, and not in the usual way (Ctrl+Z)? The checkbox ☐ DOS charset was never marked. Why does the same dialog called in two ways show different for the same file?

2Fla$her
I don't want to write long articles, so just believe me:
1. Some fonts don't have needed characters. In this case TC uses font substitution provided by Windows. In some cases it fails (f.e. for Korean language or for DOS/OEM codepages).
2. There are some problems with UTF-8 support and some other problems with UTF-16, especially in TC 32-bit and in older Windows (XP, Vista). For example, some strings aren't declared properly as Unicode, see this topic: https://www.ghisler.ch/board/viewtopic.php?t=74668

I'm going to describe some strange behaviour soon, as I can see mojibake again.