News for hackers. Stuff that matters.

A comment on APFS does not normalize Unicode filenames. Parent comment

Re:APFS does not normalize Unicode filenames by jstimpfle on Saturday March 25, 2017 @06:35AM (#13954933)
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...

[ Parent | on HN ]
Re:APFS does not normalize Unicode filenames by jfim on Saturday March 25, 2017 @03:01PM (#13957047)
> The next best thing would be to enforce a canonical (code-point?) encoding.

That's exactly what HFS+ did, and what APFS doesn't.

[ Parent | on HN ]
Re:APFS does not normalize Unicode filenames by TazeTSchnitzel on Saturday March 25, 2017 @10:22AM (#13955763)
> 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.

[ Parent | on HN ]
Re:APFS does not normalize Unicode filenames by int_19h on Sunday March 26, 2017 @04:22AM (#13959768)
The 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.
[ Parent | on HN ]
Re:APFS does not normalize Unicode filenames by ttflee on Saturday March 25, 2017 @09:08AM (#13955434)
https://turnoff.us/geek/user-space-election/
[ Parent | on HN ]
Re:APFS does not normalize Unicode filenames by jstimpfle on Saturday March 25, 2017 @09:24AM (#13955491)
That's not about filenames.
[ Parent | on HN ]