Re:APFS is not safe to use with names which have Unicode nor...
by jorangreef on Wednesday June 07, 2017 @05:22AM
(#14504771)
Yes, HFS+ implements normalization-insensitive behavior through not being normalization-preserving, in the same way that some FATs might implement case-insensitive behavior through not being case-preserving. They didn't realize that you could have both features: normalization-preserving and normalization-insensitive.
Re:APFS is not safe to use with names which have Unicode nor...
by cryptonector on Wednesday June 07, 2017 @03:31PM
(#14509221)
I guess it was a very forgivable lack of imagination. When we came up with form-preserving/insensitive we were motivated in great part by the interop mess caused by HFS+ -- we might not have arrived there without that mess, though I'd like to believe that someone would eventually have reached this conclusion regardless.
In particular ZFS has normalization-preserving/normalization-insensitive behavior, which is far superior to HFS+'s opinionated normalization-on-create (to a form that is different from the common input modes' output!).