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?
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.
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?
17 Comments
bjoern_tantau@swg-empire.de · 41 pts · 1y
Maybe the target filesystem doesn't support those filenames. I think I saw that either with NTFS or SAMBA. Really annoying.
n2burns@lemmy.ca · 31 pts · 1y
Is that a limitation of the destination filesystem?
LodeMike@lemmy.today · 13 pts · 1y
There's an Arabic name in the bottom right. Likely the software getting confused.
bdonvr@thelemmy.club · 5 pts · 1y
The filename ending left to right despite the file being right to left is kinda funny
LodeMike@lemmy.today · 4 pts · 1y
That's exactly how it's supposed to be handled.
synae@lemmy.sdf.org · 4 pts · 1y
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?
LodeMike@lemmy.today · -1 pts · 1y
Correct
ik5pvx@lemmy.world · 29 pts · 1y
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?
bdonvr@thelemmy.club · 8 pts · 1y
Unless the font if the terminal has the same issue
dsilverz@thelemmy.club · 7 pts · 1y
penquin@lemm.ee · 13 pts · 1y
butter_fly@lemmy.ml · 3 pts · 1y
Yes, those are Arabic, but Chinese, Japanese and Bangla are also affected. And I have the fonts installed.
penquin@lemm.ee · 1 pts · 1y
dragnucs@lemmy.ml · 8 pts · 1y
Never noticed that? How do you copy them, from terminal? What software do you use? What file system do you use?
butter_fly@lemmy.ml · 7 pts · 1y
nautilus, ext4
dragnucs@lemmy.ml · 5 pts · 1y
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.
Limitless_screaming@kbin.earth · 3 pts · 1y
Can't reproduce it on ext4, KDE Plasma too.
Zikeji@programming.dev · 4 pts · 1y
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?
riskable@programming.dev · 3 pts · 1y
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?
butter_fly@lemmy.ml · 1 pts · 1y
This happened when copying in batch.