Multi Commander Support Forum
Multi Commander => Support and Feedback => Topic started by: milen-prg on March 19, 2026, 14:26:07
-
Some filenames displays strange. For example:
Just create empty file with this name:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa😭.txt
It not displays at all. I use the default Segoe UI font. (Windows 11 Pro 64 bit).
IMPORTANT!!!: The display way depends on two things:
1. Must have anywhere special UTF symbol like 😭.
2. The display way differs at different name length. For example:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa😭.txt - do not displays at all (background color)
but little shorter for example:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaa😭.txt - it is shown with strange symbol for the "a" (see the attach).
At most of other length (number of symbols "a"), it displays ok (except the special UTF symbol; not completely research).
-
The issue is not encoding-related. Multi Commander appears to incorrectly handle UTF-16 surrogate pairs (e.g. emoji like 😭).
This leads to broken text measurement and rendering, especially for long filenames. The behavior depending on string length strongly suggests a layout calculation bug.
Additionally, font fallback for emoji (Segoe UI Emoji) does not seem to work correctly, resulting in missing glyphs.
The same filenames render correctly in Windows Explorer and Double Commander, so the issue is specific to Multi Commander.
-
might depend on what font you used and also other system settings. If you use a font that does not include the unicode character you enter then it can render it.
MC do not do any special processes on the filename. Windows return unicode (UTF16) name. and MC just accept what Windows give it. and then WIndows render it.
MC don't do any special processing. everything is handled by Windows. All API call in Windows are UTF16, So no special handing for it are needed
The filename you show as example works without issue for me.