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.
normalization
What do we want Apple to offer in terms of new hardware, and the problems built deep into Unicode.
The word looks identical, but uses different Unicode characters. How can you tell the difference? There are important security implications, and more.
How can you get the Unicode normalised form from within an app, or when you’re writing your own tools and scripts? unorml may be just the job.
Apple spills some of its beans to a select group of the press, and we start to explore the new features expected in macOS 10.13.
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.
