From 5aec94ad006db7a09d7e96d8959f560312b943aa Mon Sep 17 00:00:00 2001 From: "ovidiu@66ace8a8d99ce938b0538ffa0f26d30db02a9626" Date: Wed, 28 Oct 2015 13:10:28 +0000 Subject: [PATCH] --- ...ng_between_different_OSes_with_regards_to_UTF-8__63__.mdwn | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__.mdwn diff --git a/doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__.mdwn b/doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__.mdwn new file mode 100644 index 0000000000..5bbbd59700 --- /dev/null +++ b/doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__.mdwn @@ -0,0 +1,4 @@ +I'm interested in using git-annex on a freebsd system and an OSX system. +I have previously had problems with manually rsyncing due to the fact that apparently different types of UTF-8 are used namely: UTF-8 NFC & UTF-8 NFD so one option is to use rsync -a --iconv=utf-8-mac,utf-8 localdir/ mynas:remotedir/ or alternatively, I can mount the files on the NAS via a cifs share and rsync to it... + +just curios how git-annex deals with this issue or if i will run into issues due to filenames containing special characters?