Replacing " (double-quote) character

phil_a · Post by **phil_a** » 2013-04-28 12:00:48

I have some files containing the double-quote character, e.g.
Filename: On “Lord Warden” ferry.jpg

I want to change this to single-quote, as
Filename: On 'Lord Warden' ferry.jpg

Renamer log tells me "Not renamed - new name same as old name".

I tried escaping the double quote char with \", "", '", ~", %"%, but none of these worked.

Is this possible? I am using Win7.

Phil

Post by **antp** » 2013-04-28 13:10:53

The classic " double-quote character is not allowed in file names, so it must be a slightly different one. In your sample you used two different characters: “ and ” which are slightly different from the regular ".
Try copy/paste these characters from here or from the file name into Ant Renamer

phil_a · Post by **phil_a** » 2013-04-28 20:30:48

Thank you, you are absolutely correct!! The file names must have been generated in Word or something with 'proper' left and right printers quotes. I just typed (") into renamer so of course it could not find them. Cut'n'paste from the explorer listing into renamer now works fine.

Maybe a more specific log message ('find' string not found?) if you ever get time to do an update

Just want to say I find renamer an enormous help in bringing consistency to the naming convention for my thousands of photos. Especially as I keep changing my mind on the best convention

Phil

Post by **antp** » 2013-04-29 13:44:12

I could maybe change the message to "Nothing to do for this file".
Or something like you suggest, which must then depends on the selected action (as it is already the case for some of them, I think).

phil_a · Post by **phil_a** » 2013-04-29 14:12:26

antp wrote:
I could maybe change the message to "Nothing to do for this file".

That's true from the software point of view but doesn't give the user much of a clue about what s/he did wrong.

Or something like you suggest, which must then depends on the selected action (as it is already the case for some of them, I think).

Yes, the logic for user friendly error messages is not so easy. On the other hand, writing informative error message code can be easier than writing comprehensive help files that include all possibilities.