Re:APFS is not safe to use with names which have Unicode nor...
by alkonaut on Tuesday June 06, 2017 @10:54AM
(#14497671)
Wait why is a file name a sequence of bytes? Why is it not a sequence of bytes that form a valid string in some encoding, so that you can just refuse some file names? Who refuses invalid characters such as invisible characters or "/"? Would not the same place be a good place to refuse anything that doesn't normalize to the same byte sequence, or an even stricter subset?
[ Parent
| on HN ]
Re:APFS is not safe to use with names which have Unicode nor...
by cryptonector on Tuesday June 06, 2017 @01:34PM
(#14499169)
Supporting more than one encoding requires knowing what that is, and apps and APIs are very bad at keeping track of that. Which is why only Unicode in some UTF makes sense.
ZFS allows you to store non-UTF-8 if you like, but for all valid UTF-8 it implements normalization-preserving/insensitive behavior, which is the best possible compromise (IMO).