4 ms·
No offense, but I think that's a very western-centric view. Your example only make sense when the user is familiar to English (or other western languages, I gue
by blahgeek 2y ago
No offense, but I think that's a very western-centric view. Your example only make sense when the user is familiar to English (or other western languages, I guess). To me personally, I find it strange that "D.txt" and "d.txt" means the same file, since they are two very different characters. Likewise, I think you would also go crazy if I tell you "ア.txt" and "あ.txt" means the same file (which is hiragana and katakana for A respectively, which in a sense is equivalent to uppercase and lowercase in Japanese), or "一.txt" and "壹.txt" means the same file (which both means number 1 in Chinese, we call the latter one literally "uppercase number")
- ClumsyPilot 2y agoThose are all the same, I don’t see an issue
- n_plus_1_acc 2y agoWhat if Unicode updates some capitalization rules in the next version, and after an OS updates some filenames now collide and one of the is inaccessible?
- taeric 2y agoAgreed, and you could even take this into "1.txt" being the same as "One.txt". Which, I mean, fair that I would expect a speech system to find either if I speak "One dot t x t". But, it would also find "Won.txt" and trying to bridge the phonetic to the symbolic is going to be obviously fraught with trouble.
- JohnFen 2y ago> To me personally, I find it strange that "D.txt" and "d.txt" means the same file, since they are two very different characters. As a native English speaker, I agree with this.