https://bugs.kde.org/show_bug.cgi?id=466994
--- Comment #4 from John <ilikef...@waterisgone.com> --- (In reply to Andrius Štikonas from comment #1) > Changing it to uppercase was a deliberate commit: > > commit 5a30aff288fce05c540786ab9001cb0217f29494 > Author: Pali Rohár <pali.ro...@gmail.com> > Date: Tue Sep 26 19:01:20 2017 +0200 > > Set FAT label in upper case > > FAT label should be stored in upper case. Also Windows systems doing it. > > I think it is to avoid confusion to those users who actually do dual > booting. Otherwise if we enable lowercase, those users who need uppercase > for better Windows support won't know that they need it uppercase. The FAT32 specification supports lowercase / mixed-case labels: https://superuser.com/a/137576 https://superuser.com/a/1575427 With other tools, it's possible to set it as lower-case / mixed-case: https://superuser.com/a/1289605 https://ubuntuforums.org/showthread.php?t=1603044&s=d3d3bab95407af15549cd89cfc27e74d&p=10010142#post10010142 https://ubuntuforums.org/showthread.php?t=1603044&s=d3d3bab95407af15549cd89cfc27e74d&p=10018954#post10018954 https://ubuntuforums.org/showthread.php?t=1603044&page=2&p=10019023#post10019023 And the confirmation that Acronis Disk Director can do that can be seen in the section "Label characters not allowed in FAT16 and FAT32" of: https://dl.acronis.com/u/pdf/ADD12H_userguide_en-US.pdf Where is says nothing about lowercase characters or anywhere else in the document. People say that Windows does this for its backwards compatibility: https://www.reddit.com/r/explainlikeimfive/comments/i3bb3p/comment/g0agnfn/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button https://www.reddit.com/r/explainlikeimfive/comments/i3bb3p/comment/g0az3l8/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button Maybe it's little known or recently possible, but Windows can be configured to allow mixed-case too: https://www.scaledeskit.net/post/Setting-a-mixedcase-volume-label-for-a-FAT32-drive-on-Windows I find "Windows will not allow FAT or FAT32 devices to use lower case letters." is nicely put in this article: https://www.getusb.info/why-is-my-usb-name-always-caps/ Another limitation that Windows has and will not let you format drives, is the 32 GiB max partition size: https://superuser.com/a/521715 Now, considering the following things: 1. Microsoft made the FAT32 filesystem 2. Microsoft can fix / improve it, if it wants to 3. Microsoft can fix / improve, eliminate limitations to it in future Windows version or in the current ones through updates and maybe it will, one day 4. Windows can be configured to allow mixed-case 5. I don't care about Windows' backwards compatibility with it's previous versions, tools 6. I don't care if the FAT32 filesystem that I made on my computer's internal drive or external flash drive works well, or even at all with Windows, as I don't use Windows on any of my computers on which I'm going to use that FAT32 partition 7. I can already set lowercase labels with other tools, it's just a bit more annoying as have have to switch tools and possibly go into terminal to type commands 8. I did it, I tested it and it works, without problems. 9. KDE Partition manager already lets me do things that are known or supposed to not work well or at all with Windows, things that Windows, like with lower-case FAT32 labels, would not let me do, for example: -A FAT32 partition larger than 32 GiB, I just tested with 100 GiB partition and it works, it made it without any complaint, as I expected. -A Ext(2-4), F2FS, Linuxswap, lvm2 pv, unformatted which are know to not work well or at all with Windows. 10. KDE Partition manager already lets me to do things that might not be compatible with Linux itself like formatting / deleting essential partitions 11. KDE Partition manager is intended for advanced users, people who know what they are doing and / or have safe environments like new computers, new drives 12. Making a lowercase or mixed-case label is not going to trigger Windows to crash and burn, format itself, brick the computer and it's not a permanent thing, it can be tried again So why are we the Linux users or the Linux-only users who normally have the freedom to even remove the desktop environment, display server and even the Linux kernel and bootloader, limited here for the sake of Windows backwards compatibility? Even when we don't care or use Windows at all? Even when we know what we're doing? Even in a tool for people who know what they are doing? Even when you can actually do the incompatible or not working change again and again until it works the way we want or we learn something? Even when that tool does not limit / restrict other things that might not be good for a Windows environment? Where do you draw a line of what actions are accepted and what not for the sake of compatibility with Windows or Windows's backwards compatibility? What's with the restrictions and limitation of the power of KDE software for the same of compatibility with Windows? Why isn't there just a warning and let us do what we want or an option in the configuration to ignore the backwards compatibility or any compatibility with Windows instead of silently changing every label to uppercase? Honestly I find this babyproofing very annoying! And I find assumptions instead of asking or let me bypass them very annoying too! Besides the fact that this goes against the freedom that I have been used with Linux, which lets me to do whatever I want as I know what I'm doing. -- You are receiving this mail because: You are watching all bug changes.
