3 ms·
The problem exists already on the visual level, since there are pairs of distinct Unicode characters that look very much alike. I think the only thing you can
by jstimpfle 10y ago
The problem exists already on the visual level, since there are pairs of distinct Unicode characters that look very much alike.
I think the only thing you can really do about that is restricting to ASCII minus control characters. Probably many programmers would be willing to accept that, but non-technical users not.
The next best thing would be to enforce a canonical (code-point?) encoding. But given the complexities of Unicode that will get us only so far...
- ttflee 10y agohttps://turnoff.us/geek/user-space-election/ https://turnoff.us/geek/user-space-election/
- jstimpfle 10y agoThat's not about filenames.
- TazeTSchnitzel 10y ago> The problem exists already on the visual level, since there are pairs of distinct Unicode characters that look very much alike. Yes, but software doesn't consider them equivalent.
- int_19h 10y agoThe software also doesn't consider the two strings given as an example above equivalent, and for the same exact reason: they're sequences of different code points.
- jfim 10y ago> The next best thing would be to enforce a canonical (code-point?) encoding. That's exactly what HFS+ did, and what APFS doesn't.