3 ms·
HFS+ did perform normalization on a file system level and stored strings as utf-16 so it's not true for HFS+.
by bigin 9y ago
HFS+ did perform normalization on a file system level and stored strings as utf-16 so it's not true for HFS+.
- the_mitsuhiko 9y agoPretty sure normalization was done in open() and not the fs. Normalization was performed even for fat32 sticks.
- bigin 9y agoSo you disagree with the linked blog post then? I mean this entire discussion is based on the premise that HFS+ performs normalization and APFS does not. The disrcepancy means that what used to happen automatically is now the responsibility of individual applications and the author hypothises that this means that shit will break.
- the_mitsuhiko 9y agoNot sure what you want me to say. In my mind the current situation with APFS is a massive pain and was not well thought through. Previously normalization (while terrible) was at least consistent. Now different APIs have widely different behaviour and it's even worse on the application level. What used to be a annoyance has now become absolute chaos with no guidance from apple. My understanding of the article is effectively: AFPS on macOS in the current form is unusable for non-English users and I strongly agree with that. While it might be partially usable, in particular if you upgrade from an earlier mac was performed, it has a ton of really terrible edge cases most users will quickly run into.