Which String.contains() variant should you use, and how can you give access to regex searching? More answers coded in Swift 3.1.
This new version has performance improvements, and can now encode almost every character in normal English text to an obscure Unicode codepoint. Total obfuscation!
Want to hide text from electronic searching and matching? Or just explore some of Unicode’s encoding issues? Here’s a useful tool.
How T2M2 analyses Sierra’s log to assess how backups have been working. With insights into using NSDate, NSStepper, and more.
Structuring, parsing, and styling text is not difficult when you use Swift 3 as your scripting language.
What do we want Apple to offer in terms of new hardware, and the problems built deep into Unicode.
Factoring the code better to separate reading and writing the underlying data, and converting that for display.
Do you want to convert files using non-Unicode text to modern format? Or between the 144 different encodings supported by iconv? Here’s a tool to make that easy.
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.