https://bugs.kde.org/show_bug.cgi?id=521512
--- Comment #5 from Roland <[email protected]> --- Yea, it is beyond stupid that they have done this. It is probably some attempt to retain backwards compatibility, so that a file path setup on a Win10/11 machine can be used on whatever- DOS or Win98. But yea, this caught me by surprise, normally a person would assume- OK, Im running NTFS on Win64. there isnt any practical file name or path limit... And that is usually correct, except that they bolted in a bunch of Win32 apps. Anyway- again, Im only trying to perhaps save a few users some frustration if it is possible to ID a file that exceeds this 260 char path + name limit, because Windows doesnt generate a normal error- its more of an overflow clamp. And, there are just a LOT of files out there where metadata is stored in the file name itself- I see that a lot with small magazines and school websites- perhaps to make it easier for non-technical people to remember where the file was sourced etc. Anyway- not unusual to see 100 characters in a filename like that. And if you have a NAS, where the file is nested deeply, where its sort of \\Server\share\root folder\Sports\Football\High School\Team Name\Season\Game Date\FIlename.xxx, it is VERY easy to break through 26- characters. And within the Digikam environment, it seems to work transparently- moves, renames, etc. But any hook out to Explore, or drag/drop to another app, and who knows. I dont have a great solution to even suggest. I do think that the general idea Home Assistant etc have implemented works- where you have sort of a health check as part of your Maintenance routine. Maybe include something like 'Report filenames which can cause problems' type thing? I wish Windows did a proper job of generating an error message at least... But I guess since this is specific to apps and not the OS, hard to enforce. Still- their own Explore file manager?? Crazy R -- You are receiving this mail because: You are watching all bug changes.
