![os x macron 2017 os x macron 2017](https://community.adobe.com/legacyfs/online/1234680_Mac-Rond.jpg)
But the filename doesn’t exist on the disk in NFC form, so it can’t find the file. Netatalk converts the NFD filename that MacOS provides to the vol charset (set to NFC form), and then tries to look it up on the filesystem. But then MacOS’s finder asks for more information about a file specifically by name. This allows the accented characters to show up properly in MacOS and the listing looks okay.
![os x macron 2017 os x macron 2017](https://1.bp.blogspot.com/-QROoJdbFyn4/WOVdBEAoaPI/AAAAAAAABMA/9UBekIkCb2UHWOmWIfMFBrRxTaW5gVoFwCLcB/s1600/Une%2BCharlie%2BHebdo%2BMacron%2B5%2Bavril%2B2017.jpg)
![os x macron 2017 os x macron 2017](https://static01.nyt.com/images/2022/01/26/world/26france-algeria2/merlin_184509537_6e474ce4-a886-4186-ac7d-0c43e0b37779-articleLarge.jpg)
What happens is that a MacOS X client lists a directory over AFP, so netatalk converts the filenames on disk (that it thinks are NFC) to NFD (a no-op, since we’ve actually put NFD filenames on there to start with).
#Os x macron 2017 manual#
Although the netatalk manual doesn’t say it, “UTF8” actually implies “UTF8 in NFC form”, so netatalk will be unable to serve the NFD-encoded filenames that originated on my Mac correctly. This is a problem because netatalk, the AFP server on FreeNAS, expects filenames on FreeNAS volumes to be encoded in the “vol charset” which is defined in its configuration file:įreeNAS doesn’t set this explicitly, so it defaults to “UTF8”. The issue was that rsync, being Linux-oriented, preserves the filename encoding when sending files, so the filenames on FreeNAS ended up still in Mac’s NFD format (with accents encoded as separate characters). The issue came when I went to read those same files over AFP: I could briefly see folders that contained accents in the finder, but they would disappear after several seconds, then reappear 10 seconds later, then disappear again! This achieved a steady ~110MB/s, which is wonderful. So, instead I used rsync to send my files directly to the ZFS storage on FreeNAS, bypassing any of its network file system protocols. I would have died of old age before I would have been able to copy my terabytes of data to FreeNAS. However, I tried this and only achieved about 2MB/s transfer speeds. This automatically takes care of any character conversion for you. The most straightforward way to do this is to enable the Apple “AFP” network filesharing service on FreeNAS, then on the Mac, copy the files to that network share however you like. I recently set up a second computer as a FreeNAS 9.2.0 storage device, and I wanted to migrate the files from my MacBook to it.
#Os x macron 2017 series#
If anything, the standard in Linux is that a filename is just a series of bytes and the OS shouldn’t try to mangle them by converting the characters with NFC or NFD normalization forms. On Linux, I’m not sure if there is a standard, but it’s typical to find filenames encoded with NFC.
#Os x macron 2017 windows#
Windows does the exact opposite (NFC), combining the “u” and the macron together to produce a single LATIN SMALL LETTER U WITH MACRON character. This means that a character like the “ū” in the word “Jingū” is stored as two Unicode characters – a plain old LATIN SMALL LETTER U character, followed by a COMBINING MACRON character: ls | grep 2009_11_03 | od -c -tx1ģ2 30 30 39 5f 31 31 5f 30 33 20 4d 65 69 6a 69 Mac applies something called NFD to filenames before they are stored on disk (Normalization Form Canonical Decomposition). In particular, different operating systems have different ideas about how accents should be handled. Unicode (as UTF-8) is a very popular format for encoding filenames on disk, but there are some subtly incompatible variants around.