Issue 128555 - Different location for pdf export and "save as" on PC and Mac
Summary: Different location for pdf export and "save as" on PC and Mac
Status: UNCONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: configuration (show other issues)
Version: 4.1.10
Hardware: All All
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: needmoreinfo, usability
Depends on:
Blocks:
 
Reported: 2023-01-16 08:50 UTC by vulture_airforce
Modified: 2023-01-17 03:25 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description vulture_airforce 2023-01-16 08:50:42 UTC
Hi,
I am using Open office all the time and on both Mac and PC.
There are some differences in how it works, but the main thing that is annoying is when you are converting to pdf or saving files.
In Mac you press the pdf icon and you will have the same file name is suggested  and also the same folder as the original .odt-file. This is great!
When using the PC and doing the same thing you will get the same name suggested, but the folder suggested will be the root of the local documents folder.

The Mac way is much more efficient and would be preferred also on PC.
To get to the root of the documents folder is easy, but to get to at folder on a server might take a long time if you export many documents every day.
Comment 1 damjan 2023-01-16 15:55:46 UTC
By "PC", I assume you mean Windows?

For me it opens the document's directory, using the latest Git on FreeBSD, is this bug only on Windows or version 4.1.x?

Going through "git log main/fpicker", I see several bugs in our Windows file picker that were fixed in trunk but likely not backported to 4.1.x. For example bug 96720 and its commit 1aa1f6e56713546a63af3b26af83aa1655ce348c, and commit bf854bef1c48c158bb9f5e1389f8f7731b54dcdf.
Comment 2 damjan 2023-01-17 03:25:24 UTC
Even using 4.1.13 on Windows I get the same folder as the original file suggested.

Either it's a bug in 4.1.10 or I am not understanding how to reproduce this.

Can you please try 4.1.13, and if it still doesn't work, describe detailed steps to reproduce?