2 ms·
> Isn't the issue here that APFS doesn't enforce policy and instead lets the tools resolve encoding details, resulting in differences by the different tools? T
by 10000truths 5y ago
> Isn't the issue here that APFS doesn't enforce policy and instead lets the tools resolve encoding details, resulting in differences by the different tools?
The issue isn’t that APFS doesn’t enforce policy, per se. It’s that combined with the fact that its predecessor (HFS+) did, and the transition wreaked havoc on programs that came to rely on file names always being normalized Unicode.
- eesmith 5y agoWhen the file system doesn't normalize names, then wouldn't the problem be worse? That is, wouldn't different tools be built with different normalizations (or none at all)? Because that's my experience from Unix-based systems where some programs generate Latin-1 filenames and others UTF-8 names. And that doesn't even touch normalizations. What would your tool-not-policy approach be?