3 ms·
Which is a silly position since the kernel is the only thing that matters. You're right that not too many people will complain if your program crashes on non-UT
by Spivak 7y ago
Which is a silly position since the kernel is the only thing that matters. You're right that not too many people will complain if your program crashes on non-UTF-8 paths. Same with spaces in group names. 100% valid and accepted. Breaks a ridiculous amount of software if you actually do it.
But that doesn't mean it's right. It just means that we have a calcified convention.
- marcosdumay 7y ago> narrow strings are considered UTF-8 by default almost everywhere It means that this is mostly true. I dunno what it should be. There are benefits and costs on both allowing and restricting the names. As well as there are good reason for the kernel alone to support them even tough all the userland doesn't. But it does mean that you just use UTF-8 and it's done.
- user5994461 7y agoWhat's right is that the software will be basically unusable outside of the US if it's crashing on non-ASCII characters in paths. ñ é ß characters appear in every text in Spanish, French, German, etc and they go in filenames too. Imagine if a table was called a tâble in English? Surely it would be outrageous to have software crash when you try to use the word tâble.