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.
Unicode
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.
Factoring the code better to separate reading and writing the underlying data, and converting that for display.
Progress with Rosettavert to convert text encoding, including popup menus with 144 entries. But stumbling still on an issue of string encoding.
Scripting a friendly front-end for the iconv tool to convert text between 144 different types of encoding. Also how to open as well as save documents.
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.
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.
The Eclectic Light Company 