APFS does not normalize Unicode filenames

Re:APFS does not normalize Unicode filenames by yuhong on Saturday March 25, 2017 @01:26AM (#13954246)

That is due to the HFS+ normalization that APFS eliminates. The filename is stored in UTF-16 and OS X converts it to UTF-8.

[ Parent | on HN ]

Re:APFS does not normalize Unicode filenames by eridius on Saturday March 25, 2017 @01:52AM (#13954289)

Normalization and UTF-16 are completely orthogonal. It doesn't matter in the slightest whether the filesystem stores the filename in UTF-16 or UTF-8, either way it's still a sequence of Unicode scalar values, and that's what matters.

[ Parent | on HN ]

Re:APFS does not normalize Unicode filenames by kalleboo on Saturday March 25, 2017 @02:05AM (#13954321)

HFS does a lot more than convert to UTF-8. E.g. it will normalize ö to o+(umlaut), using custom normalization rules that nobody else uses.

If you tell HFS to store a file with an Ö in it, and then list the directory, the character Ö is nowhere to be found.

[ Parent | on HN ]

Re:APFS does not normalize Unicode filenames by frik on Saturday March 25, 2017 @01:43AM (#13954275)

Is it stored "real UTF-16" or in USC2 wide-chars like in NTFS? The later would be a big problem.

[ Parent | on HN ]

Re:APFS does not normalize Unicode filenames by yuhong on Saturday March 25, 2017 @06:41PM (#13957901)

I believe HFS+ was created before Mac OS supported surrogates.

[ Parent | on HN ]