Date: prev next · Thread: first prev next last
2023 Archives by date, by thread · List index




On 23/07/23 04:42, Philip Jackson wrote:
On 22/07/2023 11:02, Mike Scott wrote:
On 20/07/2023 00:14, Steve Edmonds wrote:
Does this still happen if you update to LO7.4?
If I open yyy.odt, and  click 'Save As' the field "Name" for file name is always blank.

On 19/07/2023 05:38, Philip Jackson wrote:
Hi :

I'm using 7.3.7.2 on UbuntuStudio and I'm always using 'save as' but I've never had the problem you describe. Sorry.

Philip

On 18/07/2023 16:13, Mike Scott wrote:
Hi all; a very weird issue has been found by my wife, which I can repeat on a separate machine. Both use LO 7.3.7.2 on Mint 21.

What happens is this. Take an odt file, open it in Writer then go to 'Save As'. The expected behaviour is that the filename in the dialogue box will be filled in and selected/highlighted and there'll be no file type appended. Eg, I open yyy.odt, and 'Save As' displays just 'yyy' (highlighted).

However, sometimes and for no apparent reason, the dialogue box instead displays filename and file type ('yyy.odt'), with the type (only) highlighted. This causes issues when trying to save as a different type (eg as .docx)

(TLDR: open question at end! The details of my testing results are too long; sorry.)


Thanks all for comments, including one off-list. Ap[ologies for not getting back sooner - family matters intervened.

To clarify, my made-up name yyy.odt was (previously) by way of indicating what happens, not that that was the literal file causing problems. Apologies for any mis-direction.

I'm still none the wiser as to what's happening. I've just checked again the environment for the files. I have a file in a directory /dhome/mike, and an identical copy (^C ^V in a file manager) in /dhome/mike/temp of a file called
Saturday  song sheet.odt
(yes - there are two spaces together there, but that's not the issue)

I close LO. Double-click on the one in the temp directory, head for File|Save As. The filename is filled in
Saturday  song sheet
and selected. No file type.

So, I close LO. Double-click on the one in the higher directory; again File|Save As. This time, the file name and type appear;
Saturday  song sheet.odt
the /type/ alone is selected.

I cannot for the life of me understand why the behaviour in the two cases should be different.

To add to my confusion, I've just tried the following sequence of operations, starting with the "failing" file in /dhome/mike:

make a copy and change name:
cp Saturday\ \ song\ sheet.odt yyy.odt
open yyy.odt and see that Save As prefills the file name box as "yyy.odt" with the odt selected.

Rename and do the same again:
mv yyy.odt yy.odt
Same issue - Save As shows the name and type.

Finally, do it again:
mv yy.odt y.odt
But now y.odt opens the same, but Save As simply shows a highlighted "y" in the file name box.

Oh, and if I rename y.odt back to yy.odt, the problem comes back. And, if I copy yy.odt (fails) to my temp directory, all is well with the copy.

The thing is, when trying to save as .doc having the file type pre-set in the box causes a problem - LO will try to save a .doc (or whatever) as the type shown, and it needs manually changing. That's hazardous for someone like my wife, and can potentially lose the original .odt file.

I've just tried a similar sequence with the same file in my "real" home directory (/home/mike) with identical results.


**?
Does LO perhaps treat "top-level" directories in some way specially? My current guess is that multi-character file names in a "top-level" directory are treated differently from others. That would be very odd though, so IMBW!


Thanks for reading. I find this sort of problem hard to describe concisely. Am I missing something obvious?

Hi Mike,
I've tried to replicate your series of moves listed in your latest email. I even started with a file of the same name, Saturday  song list.odt, and used mv and cp as close as I could following your sequence. In every case, when I came to 'save as' in LO Writer 7.3.7.2 in UbuntuStudio 2022LTS, only the file name without extension was shown in the 'file name' box. I tried saving into the ~/ directory and into other lower levels.

I have been unable to replicate your case where the file name and its extension are given in the 'save as' | 'file name box'.

I'm commonly working on Writer docs three and four levels down from the home directory and 'save as' is one of my most common ways of duplicating a file to provide a starter in a new directory. I've never seen the behavior you describe.

This doesn't help you, I'm afraid. Could it be something connected with your OS version? I can't exactly recall if my LO is the UbuntuStudio distribution version or whether I downloaded it from the LO website - I've done both over the years. When I look where it is installed ( usr/bin/libreoffice) I would expect I'm using the version supplied by UbuntuStudio.

Philip

I have just opened an older file, sometimes the file Name field is not blank when I "Save As" with older files until I edit and re-save. This time the full name with extension does show. If I open Writer to an Untitled document and "Save As" the Name field is pre-filled with "Untitled" (no extension).

In Tools>Options>LO>General there is an option Open/Save Dialogues, I don't know if this setting would affect Mike's result.

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.