All my LO documents have uppercase filenames followed by .odt
This uppercase-only is convenient when same document files are also shared (using samba) with windoze hosts.
When I use LO 5.x on CentOS, I can select and open document files using either uppercase or lowercase keys on keyboard.
I describe my LO 5.x as filename case agnostic.
When I use LO 7.x on FreeBSD, I can only select and open files using uppercase keys on keyboard.
Is there a way to make LO 7.x insensitive to character case in filenames, so it works like my LO 5.x ?
Or is this something handled by KDE Plasma ?
TIA’s for any tips or clues.
According to help, Open , “LibreOffice uses the native file picker dialogue box of the window manager of your operating system for the Open command.”
BTW it is a very long time since Windows 3.1 which required 8.3 upper case naming. I find that CamelCaps works best for file naming as it prevents any issues with spaces.
Thanks for the tip.
The window managers I’m using are SDDM in FreeBSD, and GDM in CentOS, so I’ll dig into SDDM and see if there’s any knobs and switches that can be tweaked.
I remember disliking any Windoze OS, and happily now rarely use it.
Our partly uppercase filenames are all just short job codes, eg ABCD.odt. It works.
I suspect that the cause may lie on the operating system level, i.e. outside the scope of LibreOffice (as you also suspected).
AFAIK:
- Microsoft file systems (FAT/NTFS) and also Apple (whatever MacOS uses, I forget the name) are inherently case agnostic towards file naming. They preserve case but do not distinguish based on case.
- UNIX file systems (at least for the System-V/Solaris/OpenBSD platforms I have worked on) are case specific. This is the context most likely pertaining to your issue with FreeBSD/LO7.
- Linux seems to be configurable. When installing Linux I have been asked (probably in “advanced setup”) whether to treat case as significant in file names. I do not know whether this is a setting for the file system or (as you suggested) a function of the user interface.
This FreeBSD forum thread about rules for file system names is perhaps a little backwards into your question, but it does offer some more insight into the matter than what I can provide, and also a pointer to the casesensitivity = insensitive setting for ZFS.
Note that this is not true for NTFS (and if “agnostic” is taken literally, not correct at all: both are at least case-preserving; case insensitivity itself means the opposite to “agnostic”, because insensitivity requires handling character case, especially tricky with Unicode and its evolution); the NTFS file system is itself case-sensitive. It’s the OS driver/API that makes operations “insensitive” (do extra work to find different-case names); one can even enable sensitive mode in Win10.
1 Like
And be careful to change here: If you had NOTE and note side by side before one of them may not be reached afterwards.
.
However - the option is sometimes useful, if you have not precise recorded names from DOS in table and TEXT.TXT is now supposed to open text.txt on the new server… But I prefer to rework the tables.
1 Like
Thanks for all the suggestions above.
You’ve given me some ideas.
All the files are currently stored in a Linux server using xfs filesystem, but may soon change to zfs filesystem on FreeBSD.
All perfectly capable of being case sensitive, and we don’t and won’t have any conflicts between ABCD.odt and abcd.odt.
I wonder whether the different window managers (SDDM or GDM) and/or flavours of LO might behave differently if remote GUI connections are made from hosts using NFS rather than Samba.
Next time I’m on-site I’ll try to check this out.