I am using Netatalk 2.0.4~beta2 on ubuntu intrepid
I have a bunch of files with unicode in their filenames. When shared to a Mac via Netatalk, they show up just fine in Finder directory listings, but when I click on them (say, to view a preview) they disappear. They show up as zero-length files to applications like iTunes. Switching to volcharset:UTF8-MAC makes them appear to work properly.
As you seem to be aware of already UTF8 is not UTF8. OS X and AFP use UTF8-decomposed, Linux uses UTF8-precomposed. UTF8-MAC is UTF8-decomposed.
The volcharset option you set must match the encoding of your filenames. As it seems they're decomposed.
In that case, IMO this should be considered a documentation bug. The docs I found /strongly/ encourage the use of the plain UTF8 default and give no clue that UTF8-MAC might be required even though the most common use of netatalk is surely to serve AFP to OSX clients.
Hint:
most if not all Linux users use plain UTF8 volcharset because thats what the native filesystem uses. Only you have a problem becaue apparently you managed to have UTF8 encoded files that are not in the OS native UTF8 encoding.
I'm not sure how to use that hint, or whether the last comment addresses the underlying problem, which appears to be as follows: a reasonable use case can result in a mysterious inability to read binary files even though their filenames present just fine in a directory listing, BUT the docs give no indication that that UTF8-MAC is a likely cure.
My files were originally created on a Mac, then copied to a Linux XFS filesystem, FWIW.
convmv -r -f utf-8 --nfd -t utf8 --nfc ./* --notest
rG0sJc qbrxaseezcvi, [url=http://jkzhztaniqvi.com/]jkzhztaniqvi[/url], [link=http://datwkutpwtal.com/]datwkutpwtal[/link], http://aisxjemanlsc.com/