{"id":32986,"date":"2021-07-01T21:23:33","date_gmt":"2021-07-02T01:23:33","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=32986"},"modified":"2021-07-01T21:23:33","modified_gmt":"2021-07-02T01:23:33","slug":"apfs-volume-names-are-still-a-unicode-mess","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/07\/01\/apfs-volume-names-are-still-a-unicode-mess\/","title":{"rendered":"APFS Volume Names Are Still a Unicode Mess"},"content":{"rendered":"

Howard Oakley<\/a> (tweet<\/a>):<\/p>\n

\n

This article stems from Thomas Tempelmann’s (@tempelorg) observation on Twitter that, if you name a volume in Disk Utility, it can remain in Unicode normalized Form C, which isn’t compatible with the rest of macOS, which expects Form D to be used.<\/p>\n

[…]<\/p>\n

If you do use Disk Utility to create two volumes with what appear to be identical names, but actually differ in their normalisation, then behaviours become stranger still.<\/p>\n

[…]<\/p>\n

The underlying problem seems to be a bug in Disk Utility, which fails to normalise volume names to Form D as the Finder does. But there’s also a bug in Spotlight indexing which results in volumes with Form C names not being indexed at all. APFS brought us many great things, but this initial design decision has only brought problems, complexity and bugs like these.<\/p>\n<\/blockquote>\n\n

Thomas Tempelmann<\/a>:<\/p>\n

To all #Mac users who have accented chars (or umlauts) in their volume (disk) name: If #Spotlight doesn’t work for you, then try renaming your volume in Finder once to “abc”, then back to your preferred name. That might fix Spotlight.<\/p><\/blockquote>\n\n

Previously:<\/p>\n