Long filename support in Picard on Windows 10

[hiccup]

@wlhlm

Here is a previous discussion that may shed some light on the state of long file name support in Picard on Windows:

Thanks for the links. It looks like this will remain an issue for a while then.

.

Picard doesn't recognize some non-Latin characters?

Normal users will not know to add a registry switch. The average user doesn’t even realise there is a limit in the OS. Otherwise they wouldn’t try and make such insanely long folder names. IMHO there are more important issues to spend time on in Picard. Allowing people to create insanely long paths will just catch the User out when the files are used elsewhere.

“Allowing people to create insanely long paths will just catch the User out when the files are used elsewhere.”

.
This is not about trying to create extremely long filenames that exceed 260 characters. It is about filenames getting truncated to very short filenames when the files you are processing with Picard are in a deeper folder structure.
That can easily happen with e.g. classical albums that sometimes have very long album titles or artist listings, or with box sets that have deeper folder structures.
Or when just having an elaborate folder structure on your PC and the files you want to process happen to be in a deep level.

I never tried using Picard’s file rename feature before, but this is probably going to be a deal breaker for me.
(it took me a day to figure out why my $truncate script wasn’t working as expected)