Unicode is wonderful, a foundation for culture, but flawed. With characters that are visually indistinguishable having different encodings, it is rotting our filenames, URLs, and strings.
Yesterday’s Keynote at WWDC confirmed that the next major release of macOS, dubbed High Sierra, will be released […]
Its annual developer conference will reveal how Apple’s new file system will roll out in macOS 10.13, and determine its adoption and success.
What do we want Apple to offer in terms of new hardware, and the problems built deep into Unicode.
Case-insensitive APFS is not at chaotic as the case-sensitive variant. But there are still plenty of problems which developers and users need to prepare for.
APFS is not currently safe to use with names which might have Unicode normalisation issues – which means it is only safe with a limited ASCII character set.
Practical demonstrations, a new free tool to explore the problem, and examples to illustrate the issues which could arise with APFS.
The switch to Apple’s new file system seems to be going very well. Except that an old problem is now becoming apparent: how to name files and folders.
It looks like this will arrive shortly on iOS devices, with 10.3. What does it offer for Macs, and when will it ship?
Sierra brings undocumented weirdness to the Finder, with a folder that is, but it isn’t, and improved Finder aliases, which don’t work as well. Yet.