Re:A brief history of APFS (Apple File System) in honour of ...
by vlovich123 on Tuesday March 28, 2023 @02:48AM
(#35336841)
I still don’t see the problem with normalization.
[ Parent
| on HN ]
Re:A brief history of APFS (Apple File System) in honour of ...
by CorrectHorseBat on Tuesday March 28, 2023 @03:34AM
(#35337116)
I guess the issue is that if you copy files between 2 systems, one which does normalization and one which doesn't. Best would be if everyone did normalization, but that ship has sailed :(
Re:A brief history of APFS (Apple File System) in honour of ...
by HPsquared on Tuesday March 28, 2023 @08:18AM
(#35339615)
Maybe each file should have two names instead of one?
Re:A brief history of APFS (Apple File System) in honour of ...
by actionfromafar on Tuesday March 28, 2023 @10:29AM
(#35341718)
MacOS at least has file ID, so there's that.
Re:A brief history of APFS (Apple File System) in honour of ...
by kalleboo on Tuesday March 28, 2023 @07:30PM
(#35349599)
And even if both systems have normalization, the normalization changes with Unicode versions, so just different OS versions will cause filename conflicts.
Re:A brief history of APFS (Apple File System) in honour of ...
by vlovich123 on Thursday March 30, 2023 @01:33AM
(#35368481)
I’m not aware of that. How do JS engines implement String.prototype.normalize?
Re:A brief history of APFS (Apple File System) in honour of ...
by hibbelig on Wednesday March 29, 2023 @09:59AM
(#35357376)
Say that each letter has two versions, and they look exactly alike. This means there are now 8 file names that look like "foo", and it's not clear which one of them you have to type in to get the file you're looking at.
Re:A brief history of APFS (Apple File System) in honour of ...
by vlovich123 on Thursday March 30, 2023 @01:31AM
(#35368471)
That’s exactly the problem normalization solves - all variants map the same.