Did this happend to anyone else?
Could it be this bug?: https://www.phoronix.com/news/Linux-Reverts-Special-Char-Uni
Maybe the target filesystem doesn’t support those filenames. I think I saw that either with NTFS or SAMBA. Really annoying.
Can you check in a terminal? If you can see them in the terminal and not in the desktop you’re missing a font. If you can’t see them in the terminal then you’ve somehow mangled them. What was the OS and filesystems you copied from?
Unless the font if the terminal has the same issue
Redirecting the output of
lsto commands such ashexdumporodwould allow to notice if the name has international characters or if they were replaced by some placeholder character (which would be represented as a repeated value across the hex dump)
Are the missing ones Arabic, too? If so, there is a “noto sans Arabic” font and other symbol fonts that you’ll need to have installed. That’s really weird, though. I have Arabic everywhere and I don’t have this issue. Did you uninstall any fonts by any chance?
Yes, those are Arabic, but Chinese, Japanese and Bangla are also affected. And I have the fonts installed.
I’d try reinstalling the plasma workspace and see if that fixes it. Or even the whole desktop.
For some reason, I assumed you have plasma installed
Is that a limitation of the destination filesystem?
There’s an Arabic name in the bottom right. Likely the software getting confused.
The filename ending left to right despite the file being right to left is kinda funny
That’s exactly how it’s supposed to be handled.
It’s been a long time since I’ve had to deal with text rendering, so forgive me if this question is silly or uses wrong terminology:
Are the unicode LTR/RTL markers part of the filename or is the display layer supposed to figure it out by the codepoints used?
Correct
Never noticed that? How do you copy them, from terminal? What software do you use? What file system do you use?
nautilus, ext4
I cannot reproduce it, I just tried to copy some files with various methods but they always end up correctly named. The only difference is that I have Btrfs. I never encountered this issue when I was using ext4 though.
Can’t reproduce it on ext4, KDE Plasma too.
Are you copying it to a locally mounted ext4 or is it a network share of an ext4 drive, and if so - what type of network share?
Could be a bug in Nautilus though it’s so mature now that would be strange. I’d report it to their repo (don’t have the link and I’m on my phone but it should be easy to find).
ext4 supports various filename encodings (simultaneously, even!) but sometimes when you copy a file from one destination to another in a batch with mixed encodings you can end up with situations like this. Especially from within a GUI.
Does the problem occur when you copy each file one by one or only in batch?
This happened when copying in batch.
