Apple now states that APFS will handle the problems of normalisation of file and folder names. At least in iOS 10.3.3 and macOS 10.12.6, due shortly.
normalisation
Apple is making adjustments to its new APFS file system for iOS. Will that bring similar improvements in compatibility to High Sierra?
This new version has performance improvements, and can now encode almost every character in normal English text to an obscure Unicode codepoint. Total obfuscation!
There are lots of different ways to modify a string, but some would turn out to be very inefficient. A gentle wander through CharacterView and a mapping closure.
Want to hide text from electronic searching and matching? Or just explore some of Unicode’s encoding issues? Here’s a useful tool.
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.
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.
