nicokaiser Posted December 12, 2013 Report Share Posted December 12, 2013 OS X stores special characters in Normalization Form Canonical Decomposition (NFD), i.e. for example german umlauts are stored as two characters ("ä"" -> a, U+0308). When syncing with a Linux client, this decomposition is also synced, so umlauts are stored in NFD on Linux also, while the rest of the Linux system stores in NFC ("ä" as one single character U+00E4). Even worse, in some situations this leads to the same file being stored twice on the Linux filesystem, once in NFD and once in NFC(as these are two different filenames). I don't know if there is an elegant solution for this, and I don't know how other sync clients (Dropbox, ownCloud) handle this. Quote Link to comment Share on other sites More sharing options...
nils Posted December 12, 2013 Report Share Posted December 12, 2013 BTsync does not currently handle any kind of file name conversion for the different available file systems or case sensitive/insensitive filesystems. I am not sure if the developers will implement this in a future version, but for the time being the best practice would be to refrain from problematic filenames if one uses multiple platforms for syncing. Quote Link to comment Share on other sites More sharing options...
goli Posted December 12, 2013 Report Share Posted December 12, 2013 Hey there. Can't you mount your btsync folder as NFC on your mac, too? There should be some parameters for "mount -o" that do that, like iconv or something.I guess I would not want to have a synchronization tool handle any file namings. Regards,Stephan. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.