I have a directory named Christian Löffler and when I rclone sync it to an rclone crypt it also appears as Christian Löffler except that it is now encoded at TIS-620 when on my local drive it is utf-8
this is on debian 9. local filesystem is ext4
my sync and mount commands are not exotic - using defaults…
Type "help", "copyright", "credits" or "license" for more information.
>>> import chardet
>>> import os
>>> chardet.detect(os.popen("ls Christian*").read())
{'confidence': 0.938125, 'encoding': 'utf-8'}
I am comparing these files with bash, so the different encoding messes with my script.
thanks for the details about the beta and --local-no-unicode-normalization - I tried it and that does make the difference. I assume there is a good reason for unicode normalisation though? Is there anything specific I should be aware of using rclone crypt?
The ideal would be a way for bash to do its own unicode normalisation. Are you aware of any such mechanism? in my testing I found that mv for example appeared to see the variations of the ö as the same. I can however create identical sub-directories in the same directory with the different ö.
Also, for the record, I think the tools mis-reported the different encodings and the remote (crypt) is utf8 and the local is something like ISO-8859-2 as it makes a lot more sense than TIS-620