Not sure if this is a bug or it is intended.
These two filenames look the same:
con pauliña.JPG
con pauliña.JPG
but they are actually different:
In the first, the ñ is a combination of 2 unicode characters:
U+006E LATIN SMALL LETTER N + U+0303 COMBINING TILDE
In the second, the ñ is:
U+00F1 LATIN SMALL LETTER N WITH TILDE
FreeFileSync for Windows will analyze folders with those files and consider that the files are duplicated with the same filename inside the same folder (something that should not be possible at least in Windows I think) which in my case helped me to clean up some bad filenames, but this might not be desired behavior.
For instance, I have now a situation in which I have in the left side only:
con pauliña.JPG
and in the right side I have both files:
con pauliña.JPG
con pauliña.JPG
and I am trying to mirror left side to right side.
Here the software should, I think, delete from the right side the one not matching, but instead it goes to "Do nothing" because "the name con pauliña.JPG" is used by more than one item in the folder. (i attached image showing this).
The same happens with characters like
í = U+0069 LATIN SMALL LETTER + U+0301 COMBINING ACUTE ACCENT
í = U+00ED LATIN SMALL LETTER I WITH ACUTE
I used https://www.fontspace.com/unicode/analyzer#e=w60 to analyze the different unicode characters.
Let me know if you need more information. Not a big deal for me, but I want to help to make FreeFileSync even better.
Some unicode characters in the filename are considered identical by FreeFileSync
- Posts: 8
- Joined: 23 Oct 2021
- Posts: 8
- Joined: 23 Oct 2021
I have just checked that after submitting my post if the difference in unicode characters have been eliminated by this forum software, so now if you copy the text in the forum for each of the 2 possible filenames you will get the same result. But I think the issue is still well explained, let me know if you have any doubts.
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
Basically this "works as designed". FFS considers this situation as a conflict, as you described. Having two files in the same folder that differ only by their Unicode representation is most likely an error that needs to be resolved manually.
- Posts: 8
- Joined: 23 Oct 2021
Alright, thanks for confirming this!