>>809
ドヤ顔で古い事言ってんじゃねーよ
リンクの中身読んでない(読めてない)のがバレバレだわ

How does Apple File System handle filenames?

APFS accepts only valid UTF-8 encoded filenames for creation, and
preserves both case and normalization of the filename on disk in all
variants. APFS, like HFS+, is case-sensitive on iOS and is available in
case-sensitive and case-insensitive variants on macOS, with case-insensitive being the default.

In macOS High Sierra, APFS is normalization-insensitive in both
the case-insensitive and case-sensitive variants, using a hash-based
native normalization scheme. In iOS 11, APFS is normalization-insensitive
as well, using either a native normalization scheme (erase restores only)
or runtime normalization scheme (upgrades from previous versions).
Runtime normalization will also be available in iOS 10.3.3 and macOS Sierra 10.12.6.
Being normalization-insensitive ensures that normalization variants of a filename
cannot be created in the same directory, and that a filename can be found with
any of its normalization variants. This means that developers don’t need to do
any additional work to ensure correct normalization behavior in these versions
of macOS and iOS.