Multi-rename tool with folders that have a dot in their name

[andres992]

Suppose I have a number of folders that contain a dot in their names like this:

Version 1.10
Version 1.11
Version 1.12

Let us now suppose that I want to append "(x)" to all the folder names, so that they would be:

Version 1.10 (x)
etc.

So I select all these folders in TC, open the multi-rename tool and... Well, I thought it would be logical to use the "Rename mask: file name" box (because I think that folders do not have extensions, strictly speaking). So I made the file name mask look like this:

[N] (x)

However, the result differed from what I expected and looked like this:

Version 1 (x).10
Version 1 (x).11
Version 1 (x).12

I have been using the multi-rename tool for years and therefore I was so sure about TC that I even did not look at the result at first and therefore messed some things up a little more.

Did I do something wrong?

I am using TC 8.52 but I could not find this behaviour changed in version 9.

I believe there could be some workaround, like e.g. writing the mask to be appended in the "Extension" box. However, that is not very intuitive and most people, I suppose, would not grasp this, at least not before they have failed once.

Therefore I propose to introduce some additional mechanism for differentiating files from folders in the multi-rename tool, in order to make the behaviour more intuitive.

[MVV]

Hmm, I agree that it would be more logical to see entire folder names in [N] and nothing in [E]...

[petermad]

It is a widespread misconception that folders don't have extensions - they do.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#naming_conventions

Naming Conventions
The following fundamental rules enable applications to create and process valid names for files and directories, regardless of the file system:
Use a period to separate the base file name from the extension in the name of a directory or file.

[Stefan2]

I believe there could be some workaround,
like e.g. writing the mask to be appended in the "Extension" box.

Yes, that is the way to go:

FROM:
Version 1.10
TO:
Version 1.10 (x)

USE:
Name || Extension
[N]    || [E] (x)




But if you think folders have no extension,
just leave the Extension box empty and put all into the Name box:

Name        || Extension
[N].[E] (x) ||





 

[MVV]

petermad,
I think that it is more important how many people want to separate name and extension for fonder names or not... And if almost no one wants, we don't need folder extensions. File extensions are important because Windows detects file type by extensions, but folder extensions are really have no sense.

[vdijken]

Changing file names (and directories) is one of the most friendly interface I have ever seen. On the fly you can see what changes and it is not much trouble finding how to do the change you want. Just use the dot in the arguments! See the attached image with the arguments I used. I took your example to do the changes.
http://www.mediafire.com/view/hfcvx5cbkbi85no/ScreenShot14.PNG

[andres992]

I did not say that batch-changing folder names in my case was impossible.

All I wanted to say was that it is not very intuitive in the case that I described, and that someone who tries this for the first time could perhaps fail at first, and would have to find his way around by test and trial. Particularly in the case of longer folder names, when seeing the new result could require one to widen the dialog box.

[bela_bacsi]

petermad,
I think that it is more important how many people want to separate name and extension for fonder names or not... And if almost no one wants, we don't need folder extensions. File extensions are important because Windows detects file type by extensions, but folder extensions are really have no sense.

+1 vote

[Stefan2]

If we want to let have folders no extension (ignore dots),
we could use a mask like
File name: [A]
Extension:
on folders.





 

[MVV]

However [A] merges name and extension for both files and folders...

[bela_bacsi]

Yes, the main purpose is the time. I wish the behavior as default for folders, with no needs to write anything.

[Stefan2]

Right MVV,
we would have to run two renaming actions,
one for files and one for folders, if that is need
and could not be handled in one run.