I specified the source folder as the target folder without enabling the
overwrite checkbox and here is how the files peoduced by SE look like:
S01E01.be05e16d-f0d5-40a2-8522-39cb0baac34f.srt
S01E02.a7d148e5-cd63-406d-b981-cefc7117ad58.srt
...
S01E11.1129e1a2-39f3-4e9d-b45f-7dfec09cfe1d.srt
S01E12.ba3debbe-93e1-43a7-8b3c-2995cc30c342.srt
while original (source) file names were like this:
S01E01.srt
S01E02.srt
...
S01E11.srt
S01E12.srt
I am not sure, but it looks as if SE is adding a GUID to original name.
While it is a good idea to use GUIDs to ensure uniqueness, it is a pain to get
rid that portion (I had to write a small app to do that).
I'd very much prefer it if SE simply refused to write back to the source folder
unless the user consciously enables overwrite.
Original issue reported on code.google.com by adem.meda@gmail.com on 20 Feb 2013 at 1:14
Original issue reported on code.google.com by
adem.meda@gmail.com
on 20 Feb 2013 at 1:14