A collection of zero-width characters, including the joiner used to create compound emoji, and others to control ligatures and line breaks.
Unicode
B+trees, directory records, directory and file names and Unicode normalisation, and whatever happened to the promise of fast directory sizing?
Text can be searched by eavesdroppers and crawlers to discover its content and extract it for other purposes. How to make their task more difficult using Unicode.
How can you have two volumes in the same APFS container with identical names? How does macOS handle the conflicts?
How can you create a new accented or other character which doesn’t appear in Unicode? It depends on whether you want it in text, or PDF.
Don’t use Unicode normalised Form C names for volumes in Disk Utility, as they cause havoc, and prevent Spotlight from indexing volumes.
Now lists the time of the start of all boots in the last 24 hours, and helps you with Unicode normalization problems.
How Café and Café are actually different, and only one of those can be a filename in macOS, despite APFS being a non-normalising file system.
When a “fixed” formatting string proves anything but fixed, then breaks without warning or even mention in a release note.
How Apple made changes to Foundation routines which format dates and times which can break their formatting when in 12-hour clock mode.