So programs that show the filename in the title bar: how do they display it? Really big title bar? Align the title bar on the left or right? What if I mix english and Kannada? What then?
Or what if I start with an english word in the terminal, and then switch to kannada, what's the terminal supposed to do?
I haven't used a lot of asian language systems, but I'm going to guess two things that I'm pretty sure are true:
A) they're already implicitly dealing with these restrictions, whether the file system enforces it or not
B) they probably already have workarounds to deal with these cases anyway. (alternate scripts or whatever).
Regardless of culture, I'm going to make what I think is a pretty obvious statement: good filenames are easy to type and unambiguous. If your filename is neither of those, it's not a good filename. The point of a filename isn't to be as expressive as possible, it's to be universal, descriptive, and easy to work with. None of that requires special characters.
With regard to the space thing, I think it's overblown. Spaces are common enough that good software engineers think to handle it. Newlines in files? I've /never/ seen that, even though it's possible. Also, space doesn't require an escape character. Once you start getting to newlines, it does. Once you start introducing escape characters into it, it's an entirely new layer of complexity.
That hardly sounds like a file-system issue. That's an application and UI-design issue.
Just because you think some of these issues are hard and you don't know how to deal with them on an application level (beacuse you haven't had to yet), doesn't make that a valid reason into limiting the capabilities of the file-system.
It is a problem when you have languages with fundamentally different rules trying to share the screen, and that is also not a culturist observation; indeed one would think that denying this would be the culturist position.
Of the various points I mentioned, in modern times this is probably the least important, now that RAM, ROM, and CPU are so dirt cheap. This wasn't always true.
That's what transliteration is for. I have no problems writing my name transliterated into the Latin script.
Simple enough for a Western language speaker, sure. Pretty inhibiting for a speaker of Kannada that they can't name their résumé file with their own name.
> Require that every program that handles files in some capacity can handle every single possible weird unicode and control code subtlety in existence?
I assert again that once you allow spaces, you're already in the situation that you need to treat filenames as sequences of bytes that need quoting.
Also, I want to point out again that almost all of these problems are only when writing shell scripts. C programs or e.g. GUI applications with file pickers tend (with exceptions of course) to not have these problems since you get the filenames into them.