Back-Up File Names

[GoogleCodeExporter]

I was doing some general maintenance on my Google Docs today and noticed that 
several files said "BACKUP" instead of "SKIP" when I knew they were unchanged. 
This happened with about 10 files. I decided to investigate and found that I 
had 2 files with the same name in the same folder in Google Docs. This is 
allowed in Google Docs, but obviously does not work when you download the files 
back to your computer. I just thought you would like to hear about this in case 
someone ever writes you with the same issue. I ended up re-naming the files in 
Google Docs. I re-ran the program and everything was labeled "SKIP", just as it 
should be.  

Original issue reported on code.google.com by chaddres...@gmail.com on 26 Mar 2011 at 8:36

[GoogleCodeExporter]

Yes. You're right. It's a know limitation of GDocBAckup. I wrote FAQ#9 about 
that. http://gs.fhtino.it/gdocbackup/faq
I'm planning to introduce a "warning sytem": if GDocBackup found a "collision" 
it throws a "warning" (MessageBox?).
I'm also thinking about a completely different local storage for exported 
documents.

Original comment by fht...@gmail.com on 27 Mar 2011 at 8:16

• Changed state: Accepted
• Added labels: Milestone-0.5.0

[GoogleCodeExporter]

What do you think of numbering the duplicately-named files sequentially? (e. 
g.: 3 files named Document.odt would become Document.odt, Document(2).odt, 
Document(3).odt)—that is how Google Docs handles them when they are zipped.

Original comment by ecw.tech...@gmail.com on 3 Apr 2011 at 7:38

[GoogleCodeExporter]

I think it would work. I also think an error message telling the user that
duplicate file names exist would be just as good. Whatever is easier.

Chad

Original comment by chaddres...@gmail.com on 3 Apr 2011 at 8:43

[GoogleCodeExporter]

@ecw.t...
Good idea but there is a problem.  On the first run your solution is good. But 
there is not a "link" between the files on Google servers and the backed-up 
file locally. So GDocbackup will not be able to detect what files changed and 
what files are the same.
Perhaps there is only one solution: store files locally using the Google doc ID 
 (0AtkSHSg5lGq4dEJ2Y1Z4MmRfZ0taZ.....) and store meta-informations in a small 
local db (name, last modify date, folders (tags), etc...).

Original comment by fht...@gmail.com on 4 Apr 2011 at 5:55

[GoogleCodeExporter]

Added a warning message.
ver. 0.4.30.129

Original comment by fht...@gmail.com on 25 Apr 2011 at 9:33

• Changed state: Fixed