Summary: | Windows-centric filename patterns | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Henry Pfeil <hpfeil> |
Component: | Copying | Assignee: | k3b developers <k3b> |
Status: | RESOLVED NOT A BUG | ||
Severity: | wishlist | CC: | michalm, myusualnickname, trueg |
Priority: | NOR | ||
Version: | 24.04.80 | ||
Target Milestone: | --- | ||
Platform: | Slackware | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Henry Pfeil
2024-05-09 19:11:45 UTC
spaces are allowed in windows and in linux. I am hoping to help keep filenames confirming to rules of as many systems as practical/reasonable. Windows/Mac/Linux... There are many variations in all of that that I am not familiar with, but I would want to limit the path to 256 characters, and typeable characters, no emojis, no escape characters... where /and \ are only used for directory I looked at the relevant code. This problem lies with the CDDB database. It appears that the db is sullied by children misusing Windows submissions: full of spaces, apostrophes, parentheses, semicolons, commas, mixed case, different languages and all. This would be a monster task to impose standards-compliancy upon the existing entries, not so much for new entries after the screens are in place. A few sed and tr statements in the get-cddb functions would fix it, but violations of file-naming standards is in cddb.org, not K3b. Since it is relatively easy for me to fix the mess in post-processing, this is not a bug. Who knows who enforces international file-naming standards. Me, I'm more focused upon 'works only in Windows' webbage, making folks aware of https://validator.w3.org and http://www.anybrowser.org/campaign when I can no longer log in to pay my bills because some moron hired a code jockey who is capable only of manipulating a Windows html-design gooey. |