Case sensitive unix vs non case sensitive win + sync = pain

[limex]

Hi,
I think you should change the behavour for the following use case:

- Syncing from a UNIX file system to win.
- Among 1000s of files in 10s of folders: many files like i.e. File.txt and file.txt
- When syncing: TC complains about these files one after one and the sync stops.
- I have to remember the place where the files are. That sucks most!
- Go through the nested folders and delete one.
- Repeat for the next hours until all files are synced.

I think your want to add a dialog similar to the handling of already existing files during the sync: overwrite, rename, overwrite older, ....

Sorry for my frustration, but after hours of watching TC scanning the same folders again and again for 1/2h 10 times or more, U ARE frustrated believe me.

Running TC 7.04a.

Regards

[sqa_wizard]

With TC 7.50 you get rid of the multiple warnings at least.

16.08.09 Fixed: FTP, Synchronize dirs: Warn the user only once about files with same name but difference case (e.g. 'a' and 'A'), even if there are multiple

[Flint]

This fix was for FTP only, there are still such things as plugins like SFTP, and network Samba servers with Linux OS.

[limex]

With TC 7.50 you get rid of the multiple warnings at least.

16.08.09 Fixed: FTP, Synchronize dirs: Warn the user only once about files with same name but difference case (e.g. 'a' and 'A'), even if there are multiple

Nope. I get an ERROR, not a WARNING. A warning (at least from my IT experience) lets the app proceed the task. This here is an error that stops the sync!
And only showing the first error and not all doesn't really solve the problem. That is: Assist in dealing with ALL these Case Issues. Making it still a painful manual job.

Messagebox with OK Button:
Error, two files with the same name but different case exist on the remote server! Because windows bla bla bla
images\M5-3.jpg
images\m5-3-jpg

I didn't find a new setting in config of TC 7.5a that makes a warning out of the error. If I was to blind to see, I'm sorry. Please advice where it is.

[limex]

be careful not to use parts of 0.1.2 that are not available in 0.1.1, such as ies lights....

sorry, but what PARTS are you talking about? Are you talking about plugins? And why 0.1.x as Version?

My problem is related to Sync via FTP.

[fenix_productions]

2limex
sophieb seems to be spam bot. Don't worry about it

[ghisler(Author)]

This here is an error that stops the sync!

Actually it is an error, TC cannot handle the situation of multiple files with the same name but different case.

Imagine this case:
Left side (local):
test.txt

Right side (remote):
Test.txt
TEST.TXT

Normally TC maps the file on the left with the file with the same name on the right (case-insensitive).

In the case above, this isn't possible. TC would have to upload test.txt and download both Test.txt and TEST.TXT, which is impossible with the case-insensitive Windows file systems.

[Balderstrom]

Xnews and other newsreaders handle such collisions by appending a numerical count to the end of the file.
Save 12 files called Test.txt from a news mbx and you'll wind up with something along the lines of:
Test.txt, Test_0.txt, Test_1.txt, Test_2.txt, Test_3.txt, Test_4.txt, Test_5.txt, Test_6.txt, Test_7.txt, Test_8.txt, Test_9.txt, Test_10.txt, Test_11.txt

Others might just add a repeating 1, or aa, ab, ac, etc.

[ghisler(Author)]

Hmm, but with each sync pass, you would get more and more copies of the same file this way, and the files with appended numbers would be uploaded too...

[Balderstrom]

The collisions could be displayed in the list of the SyncTool with inverted fg/bg colours, and a pop-up after [ Compare ] - which indicates there are *nix windows file collisions:
[Rename] [Skip]

Choosing [Rename] would rename the files in question to a default pattern "count" (possibly allow the user to set/override this pattern in the INI).

[ghisler(Author)]

Hmm, yes, I could show the duplicate names, but disable the lines from synchronizing - these files would then remain untouched. The user would be able to delete them manually via right click menu only. What do you think?

[Balderstrom]

That'd work, of course this is an instance where my previous wish of ability to manually (inline) rename a file within the SyncTool would be useful too

[limex]

This here is an error that stops the sync!

Actually it is an error, TC cannot handle the situation of multiple files with the same name but different case.

Imagine this case:
Left side (local):
test.txt

Right side (remote):
Test.txt
TEST.TXT

Normally TC maps the file on the left with the file with the same name on the right (case-insensitive).

In the case above, this isn't possible. TC would have to upload test.txt and download both Test.txt and TEST.TXT, which is impossible with the case-insensitive Windows file systems.

Sorry forgot to mention that I used Asymmetric Sync. In your case listed above from right to left.
The Workflow as it should be:
- TC detects the 2 problematic files (what it does already cause the 'Warning' Message lists them up
- Ask me which one to choose for syncing to the left
- Syncs that file
- deletes all other unter problematic files from the list from the right side
- done!

There is NO conflict in this situation that TC is not able to handle. If I am right. I expect I am. hopefully

[ghisler(Author)]

Hmm, but then you would be back at the situation where 100 double names cause 100 dialog boxes (this time to choose the one to copy)...

[Balderstrom]

Do the DialogBox:

• Once per Conflict.
• Only after Synchronize is clicked.
  • Only IF more than 1 conflicted file are selected for Syncing.

An Additional File Filter: [↓] (Drop Down Menu) to the right of [Duplicates]

• Contains 1 line per conflict (example):
  • Show conflict #1 only
  • Show conflict #2 only

Once you have filtered/displayed the conflicting files, you need to select ONE for syncing and the others need to be unselected.

Possibly one additional action on the DropDown [↓] "Unselect ALL File Collisions." -- not sure if this is necessary, but might be useful.

So if you have, TEST.txt, Test.Txt, TeSt.txt --- that is ONE collision set.

Once you do the compare you can be notified there are collisions, please resolve them.
You go to the [↓] drop down;
choose "Show Conflict Set #1 Only"
Select the file you want to be Sync'ed.

Now you Press [Synchronize] -- so long as only 1 file of a collision set is selected for sync'ing then there is no DialogBox popup. If there is more than one selected, a dialog box pops up notifying as before: there are collisions, please resolve them -- in this case it could indicate specific files, but again only once per collision set.


NOTE: The new [↓] drop down: could be expanded upon in later TC Versions, as a place to add plugin-filters, or other such things that might be deemed useful.