[notabug] 896 - Rename fails when only changing upper and lower case

[larsen]

I thought I had already posted this, but couldn't find it, so maybe this is a duplicate.

Steps to reproduce:
- Start renaming a file "This is a test"
- Change "test" to "Test" and press Enter

The file will still be named "This is a test" instead of "This is a Test".

Workaround:
- Rename to "This is a xTest"
- Rename again removing the x

FC 896 64-bit, Windows 10 22H2 64-bit.

[ralfso]

AFAIK the filenames "This is a test" and "This is a Test" are the same names for Windows (NTFS-filesystem).
They can't exist in one directory as two files.

https://learn.microsoft.com/en-us/windo ... ensitivity

So the rename istn't a rename.
Only Linux-filesystem is differencing case-sensitive filnames.

You have to modyfy the case sensitivity of directories for windows with case sensitivity flag (see microsoft link).

But I don't know if FC can show this.

[larsen]

It's true that those files normally cannot exist in one directory. Didn't knew about the flag.

However, there is a difference in those names and each one can exist on its own (just not in the same directory).
Also, Windows Explorer is able to do such a rename without a workaround.

[Forez]

Say what?

I have been changing in FC cases of items on my GPT NTFS volumes left and right since whatever without a sweat, using both the Multi Rename feature and by hand method

[larsen]

Just to verify: You ONLY changed upper/lower case WITHOUT changing any other part of the filename?

[Forez]

Yes. And although I think thorough the years I have encountered some programs that could not do this, so far FC has not been one of them

[Dreamer]

I can confirm, that renaming "test" to "Test" works good in the latest version and also in 880 32-bit, default settings, Windows 10 22H2 64-bit.

[larsen]

Got it: Renaming works on NTFS file system, but not on FAT32 or exFAT (neither in Windows Explorer).

[Forez]

Good to know