Normalises strings to any of the four standard Unicode normalisation forms C, D, KC or KD, supplied with source.
The good (Xcode 9, Swift 4.0), the bad (iTunes 12.7), and the less accessible (iOS 11), as Apple’s month of upgrades progresses.
Which String.contains() variant should you use, and how can you give access to regex searching? More answers coded in Swift 3.1.
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.
A command which is seriously pernickety about its parameters, and sends all its output to the standard error stream. Such fun.