On Jun 6, 2017, at 7:29 AM, Stephan Beal <sgb...@googlemail.com> wrote:
>
> i just stumbled across this and figured it might someday become a bug
> report against fossil:
>
> https://eclecticlight.co/2017/04/06/apfs-is-currently-unusable-with-most-non-english-languages/amp/
That article is written by a proponent of Unicode normalization at the
filesystem layer, but that is not a universally-held opinion.
Consider this thread for contrast:
https://news.ycombinator.com/item?id=8876319
tl;dr: HFS+ sucks because it does Unicode normalization, but extfs doesn’t, so
yay Linux.
ZFS supports normalization at the filesystem layer, but the default is “none”.
You have to request normalization at filesystem creation time. Unlike most
other ZFS properties, you cannot change this one after the filesystem is
created.
In other words, Apple is simply choosing to follow the rest of the POSIX world
here.
As far as I can tell by Googling alone, NTFS also behaves this way: that is, it
stores the file name as given by the application without doing its own
normalization.
It appears that Apple has simply stopped Thinking Different. :)
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
