Batch Rename - Partially Mixed Case / Generic Text Replace

[Dreamer]

Add "Partially Mixed Case" to the Filename Case in Batch Rename - name - mixed case, extension - lower case...
e.g. - old name 'IMAGE NUMBER 1.JPG', new name 'Image Number 1.jpg'

Edit: another suggestion - Convert Underscope ("_") to space

Minor suggestion - add undo feature for Batch Rename (not sure if it would be possible...)

Thank you!

[xnview]

Add "Partially Mixed Case" to the Filename Case in Batch Rename - name - mixed case, extension - lower case...
e.g. - old name 'IMAGE NUMBER 1.JPG', new name 'Image Number 1.jpg'

Are you sure that it's a needed option?

[Dreamer]

Add "Partially Mixed Case" to the Filename Case in Batch Rename - name - mixed case, extension - lower case...
e.g. - old name 'IMAGE NUMBER 1.JPG', new name 'Image Number 1.jpg'

Are you sure that it's a needed option?

I think, it would be more needful/useful than existing items in Filename Case (and maybe not hard to implement)

Another idea: There are many (downloaded) images in this format: "image_number_1.jpg"

So what about "[x] Convert underscore '_' to space ' ' " option in the Batch Rename dialog box?

Finally (after "Partially Mixed Case" and "Convert underscope to space" options would be used), the image name would be: "Image Number 1.jpg"

[helmut]

Add "Partially Mixed Case" to the Filename Case in Batch Rename - name - mixed case, extension - lower case...
e.g. - old name 'IMAGE NUMBER 1.JPG', new name 'Image Number 1.jpg'

Are you sure that it's a needed option?

I don't use the batch rename very often, but the "First letter uppercase" sounds useful to me. (Perhaps it has something to do with German, in German we use upper/lower case when writing, a lot.)

From my point of view, the "First letter uppercase" is needed for the name, only, not for the extension. (Think extension should be lowercase, always). This will limit the number of additional menu items, a bit.

[Dreamer]

Add "Partially Mixed Case" to the Filename Case in Batch Rename - name - mixed case, extension - lower case...

Are you sure that it's a needed option?

I don't use the batch rename very often, but the "First letter uppercase" sounds useful to me.

From my point of view, the "First letter uppercase" is needed for the name, only, not for the extension. (Think extension should be lowercase, always). This will limit the number of additional menu items, a bit.

Exactly! I think, many xnview users have got images from the internet or digital camera in the format: "aaaaa_bbbbb_1.jpg" or "AAAAA_BBBBB_1.JPG", so I think both features ("Partially Mixed Case" and "Convert underscore to space") would be very useful... Finally the name would be "Aaaaa Bbbbb 1.jpg"

[xnview]

Exactly! I think, many xnview users have got images from the internet or digital camera in the format: "aaaaa_bbbbb_1.jpg" or "AAAAA_BBBBB_1.JPG", so I think both features ("Partially Mixed Case" and "Convert underscore to space") would be very useful... Finally the name would be "Aaaaa Bbbbb 1.jpg"

Ok

[helmut]

As written before, I think that the "First letter uppercase" is useful and should be added.

But I'm not so sure with the [x] Convert underscore to space checkbox. This might be useful, but I think this is a very special and very limited option:

- User A exactly wants [x] Convert underscore to space. Lucky him/her.
- But user B might want [x] Remove underscore.
- And user C wants [x] Remove underscore and capitalize next letter.

Just some possible and not too unlikely examples. At the moment I have no more general approach and solution. I just wonder...

[Dreamer]

But I'm not so sure with the [x] Convert underscore to space checkbox. This might be useful, but I think this is a very special and very limited option:

- User A exactly wants [x] Convert underscore to space. Lucky him/her.
- But user B might want [x] Remove underscore.[/

I think most users want "Convert underscore to space", not "Remove underscore"

e.g. original name - grand_theft_auto_01.jpg
after "Convert underscore to space" - grand theft auto 01.jpg
after "Remove underscore" - grandtheftauto01.jpg - I don't think somebody wants this

- And user C wants [x] Remove underscore and capitalize next letter.

I don't know any file manager with this feature and I don't think this would be useful for many users.

Of course, the best feature would be "Replace <word A> with <word B>" (but I don't know how complicated it would be to implement this...)

Some examples: (original name / new name)
Replace <_> with < > (grand_theft_auto_01.jpg / grand theft auto 01.jpg)
Replace <image_00> with <Holidays > (image_0001.jpg / Holidays 01.jpg)

Of course, features "Replace <word A> with <word B>" or/and "Convert underscore to space" would be applied before "Partially Mixed Case".

[Lostclown]

In my opinion the "Batch rename" tool of XnView is an extra feature.
It should be relatively simple as there are specialized rename tools available that will always be better than XnView at this task.

The strength of this feature in XnView is the ability to include image properties and EXIF/IPTC data into the file name.

The suggestion of adding a new "First uppercase" is good in my opinion.

But removing underscores and generic text replace should be excluded in XnView. And this is of course all simply in my opinion
Personally I would be more likely to want to replace spaces with underscores than vice versa. It is probably easy to find many useful features of this kind, but they would clutter this tool in XnView too much if all included.

Lostclown

[Dreamer]

In my opinion the "Batch rename" tool of XnView is an extra feature.
It should be relatively simple as there are specialized rename tools available that will always be better than XnView at this task.

But removing underscores and generic text replace should be excluded in XnView. And this is of course all simply in my opinion
Personally I would be more likely to want to replace spaces with underscores than vice versa. It is probably easy to find many useful features of this kind, but they would clutter this tool in XnView too much if all included.

I don't agree. I use two different file managers for that ("Partially Mixed Case" and "Convert underscore to space") and it's not very comfortable.

XnView's got many extra features, but everything is very simple, intuitive - and that's the reason why we all use it/like it.

Multiple File Convert dialog's got more options and I think it's still simple and intuitive, so I don't think that option "Convert underscore to space" or "Replace <word A> with <word B>" would be "clutter".

There are many "rename" options in xnview, but they are a little bit useless if we must use also other tool for other feature... and I think (at least "Convert underscore to space") would be very useful.

[Lostclown]

I don't agree. I use two different file managers for that ("Partially Mixed Case" and "Convert underscore to space") and it's not very comfortable.

I understand your point of view. And I also think it is perfectly normal that we disagree on this. I use a single file rename utility to rename files (that can do both "Partially Mixed Case" and "Convert underscore to space" and vice versa) and then I use XnView to include image metadata in filenames (and enjoy the images of course).
This tool I use is called CKRename, has a very simple interface and does everything I need it to do, and is freeware
See: http://www.musicsucks.com/CKSoft/index.htm

The problem here is to decide what is useful for many users and what is useful for a few or only a single user.

Multiple File Convert dialog's got more options and I think it's still simple and intuitive, so I don't think that option "Convert underscore to space" or "Replace <word A> with <word B>" would be "clutter".

Very true.
But the heart of XnView is image viewing an manipulation, but not file renaming.
If the following options would all be added

• Convert underscore to space
  Convert space to underscore
  Remove underscore

it might be starting a clutter trend and I would think a generic replace as you have suggested would be better, as it can handle all of the cases above plus a lot more.

There are many "rename" options in xnview, but they are a little bit useless if we must use also other tool for other feature... and I think (at least "Convert underscore to space") would be very useful.

OK.
But my point is that I am willing to use more than one tool if each of them does their separated tasks well. My felling is that if a single tool is meant to do everything very well then it is likely to loose focus and instead of doing few things very well it will do many things not as well.

Or maybe I am just being paranoid
Feel free to disagree.

Lostclown

[Dreamer]

I use a single file rename utility to rename files and then I use XnView to include image metadata in filenames.

You can see now, you must use also 2 tools for that

The problem here is to decide what is useful for many users and what is useful for a few or only a single user.

Yes and I think it would be very useful for many users, why you think it doesn't?

Multiple File Convert dialog's got more options and I think it's still simple and intuitive, so I don't think that option "Convert underscore to space" or "Replace <word A> with <word B>" would be "clutter".

Very true.
But the heart of XnView is image viewing an manipulation, but not file renaming.
If the following options would all be added

• Convert underscore to space
  Convert space to underscore
  Remove underscore

it might be starting a clutter trend and I would think a generic replace as you have suggested would be better, as it can handle all of the cases above plus a lot more.

There are many "rename" options in xnview, but they are a little bit useless if we must use also other tool for other feature... and I think (at least "Convert underscore to space") would be very useful.

OK.
But my point is that I am willing to use more than one tool if each of them does their separated tasks well. My felling is that if a single tool is meant to do everything very well then it is likely to loose focus and instead of doing few things very well it will do many things not as well.

Or maybe I am just being paranoid
Feel free to disagree.

Lostclown

Why there is always "but" ?

I don't want all that options (above).
Of course just "Partially Mixed Case" and "Generic replace" features would be better and maybe "generic replace" would be not more difficult to implement than "Convert underscope to space", I don't know, just Pierre...

Look at "Insert>>" button, how many features there are, i don't think one more feature ("Generic replace") would be confusing, there is enough space there, e.g. beside "Start/Step"

Code: Select all

Start: [1   ]    Replace: [    ]
Step:  [1   ]    With:    [    ]

[xnview]

Code: Select all

Start: [1   ]    Replace: [    ]
Step:  [1   ]    With:    [    ]

Ok, i add Replace/With because i think these option is important too
It's only a pattern replace of original name?

[Dreamer]

Code: Select all

Start: [1   ]    Replace: [    ]
Step:  [1   ]    With:    [    ]

Ok, i add Replace/With because i think these option is important too
It's only a pattern replace of original name?

Great, thank you

Some examples:
- original name "image_0001.jpg"
- replace [image_00] with [Holidays ]
- new name "Holidays 01.jpg"

- original name "grand theft auto san andreas 01.jpg"
- replace [grand theft auto] with [GTA]
- new name "GTA san andreas 01.jpg"

The order is also very important, "Replace" must be applied before "Partially Mixed Case"...

Example:
1. original name "grand_theft_auto_san_andreas_01.jpg"
2. replace [_] with [ ]
3. perform "Partially Mixed Case"
4. new name "Grand Theft Auto San Andreas 01.jpg"

but...
1. original name "grand_theft_auto_san_andreas_01.jpg"
2. perform "Partially Mixed Case"
3. replace [_] with [ ]
4. new name "Grand theft auto san andreas 01.jpg"

[helmut]

Code: Select all

Start: [1   ]    Replace: [    ]
Step:  [1   ]    With:    [    ]

Ok, i add Replace/With because i think these option is important too
It's only a pattern replace of original name?

Perhapse an option "[x] Case sensitive" might make sense, too.