2919
7 months, 3 weeks ago
—
7 months, 4 weeks ago14 of 14
Tip Reveddit Real-Time can notify you when your content is removed.
your account history
Tip Check if your account has any removed comments.
view my removed comments you are viewing a single comment's thread.
view all comments
[removed]
Restore AllHide Unarchivedhow odd
I thought Linux could handle any character but / in file names
How could Arabic people use Linux if it doesn't accept Arabic characters?
The name of the character is ARABIC TONE ONE DOT ABOVE, which seems to be placed above the character preceding it. The character before it in the filename OP had was a space, which might not be able to be combined with the dot
That's an interesting behaviour
because it's about nautilus, the explorer, (gnome software) - not linux itself
edit: or a text library as op said
But what libraries is it using for file system access. I don't think nautilus is the only program that will be affected
It has most likely nothing to do with the file system. Most file systems care very little about file names. Instead, I am 100% percent certain that this can be attributed to a buggy font renderer.
I have configured my zfs filesystems to accept only valid UTF8 filenames.
Yes and I've forked ext2 to only allow writes on blood moons
Wow, do you feel cool?
It works fine with Arabic characters… well, sometimes due to missing (or really bad) fonts it can be a bit of a pain, and any text editor that has ligatures disabled will render Arabic text incorrectly.
P.S: I didn’t even know that this character existed in Unicode. Apparently it’s part of the “extended Arabic” Unicode set, which includes many characters that I cannot type on my Arabic keyboard. I think it’s unlikely that a user would run into that specific character to cause Nautilus to crash.
You can use ∕ in filenames :-)
So it is similar to the effective power or black point bugs, at least in the broad categories?