-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
2.9
-
None
-
Windows 10 22H2
Title says it all. When you save a previously tagged album with modified capitalization of some tag value the filename script uses, the new capitalization is not reflected in the destination path. This is the case for both folders and files in place. However, if a file is being moved out of its original location, the file's name does change to reflect the new capitalization.
Steps to re-produce:
- Add a previously tagged album to Picard.
- Change the capitalization of any tag value that is used as part of the filename script in use. For example, the album title if that forms part of the destination path as dictated by the filename script in use.
- Click "Save".
- has related issue
-
PICARD-1991 Case-only changes to file names are not applied on case insensitive file systems on Linux
-
- Closed
-
-
PICARD-1992 Case-only changes to file names are not applied on FAT32 and exFAT file systems on Windows 10
-
- Closed
-
I had considered this when implementing
PICARD-1991andPICARD-1992. This is somewhat tricky to implement.The core thing is, that because Windows is case insensitive independent of the casing it is considered the same directory. So you can't create a second directory with separate casing.
The above tickets implemented the case changes for individual files. This would need to be done for every directory in the hierarchy. So instead of just saving the file Picard would need to check each directory for casing changes and apply the renaming.
Things get complicated by a few things:
Overall it ads quite some complexity to the file renaming / moving for a case where the file essentially is kept in place without effective path change.