2 ms·
There doesn’t seem to be any way to fix this issue though? Unless you mean breaking the standard such as forcing special behaviour for this particular character
by MichaelZuo 5y ago
There doesn’t seem to be any way to fix this issue though? Unless you mean breaking the standard such as forcing special behaviour for this particular character such that it simply cannot be used in a filename. But that would defeat the purpose of Unicode, it would turn, at the very least, into Duocode.
- marcosdumay 5y agoHum... Most standards allow that kind of special cases. For filenames, POSIX doesn't, but your viewer can render it on any way (and it already renders many dangerous characters - ASCII had them too - in non-obvious ways).
- MichaelZuo 5y agoThis wouldn’t be a standard allowing a special case, it would be forcing all current and future machines to implement a special case. What if one vendor decides not to care? Then there would be a de facto split, it’s likely why the unicode committee doesn’t directly fix the issue.