https://bugs.kde.org/show_bug.cgi?id=510174
--- Comment #9 from Roke Julian Lockhart Beedell <[email protected]> --- (In reply to David Redondo from comment #8) > media types may be case insensitive but file extensions surely not Based upon what? I ask because, as my own knowledge, and the undermentioned citations corroborate, filesystems like FAT (and VMS's ODS-3) store all filenames as upper-case, [^1] [^2] and all Win32 filesystem APIs are case-insensitive. This matters to us, because I've yet to encounter any software in my lifetime that would treat `.PDF` as an entirely different file type to `.pdf`. I am certain you've not, either. This is especially because, outside of Windows (that is, on all XNU/Darwin and Linux-based OSes), file association is performed my Media Type! In that context, special-casing file extensions in solely KDE's file chooser portal doesn't make any sense, when it's not a determiner that this DE uses. [^1]: https://lists.debian.org/debian-user/2009/09/msg00443.html [^2]: https://superuser.com/revisions/862283/2#:~:text=The%20original%20FAT%20file%20systems%20actually%20stored%20the%20files%20names%20(and%20extensions)%20as%20all%20caps%2C%20regardless%20of%20how%20you%20entered%20them%20(making%20it%20'case%2Dinsensitive'%2C%20but%20not%20'case%2Dpreserving'). Perhaps, explaining my rationale is more convincing: I often need to download a file with a specific filename, so that it can be submitted with a specific filename. I'm going to need to rename it, because the person requesting that file wants it with an upper-case file extension. Making me rename it is nonsensical, as is appending another, redundant file extension (because file extensions are redundant on Linux anyway; I'm adding the extension for Windows users). -- You are receiving this mail because: You are watching all bug changes.
