Bug 156840

Summary: Add source path as property to embedded image file
Product: LibreOffice Reporter: Robert Pollak <robert.pollak>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: enhancement CC: heiko.tietze
Priority: medium    
Version: 7.0.4.2 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:

Description Robert Pollak 2023-08-21 13:12:27 UTC 
Description:
I often need to know the original filename of an embedded image, e.g. to know which parameters and data I used for creating a diagram. It would be useful if this were available as a property after embedding an image file.

Also see: https://ask.libreoffice.org/t/writer-how-to-show-the-embedded-images-path-and-filename/51858

Steps to Reproduce:
1. Embed an image file.
2. Try to get the original path and filename from within the Writer document.


Actual Results:
The original path and filename is lost.

Expected Results:
The original path and filename is shown as image property.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.0.4.2
Build ID: 00(Build:2)
CPU threads: 40; OS: Linux 5.10; UI render: default; VCL: x11
Locale: en-US (en_DK.UTF-8); UI: en-US
Debian package version: 1:7.0.4-4+deb11u4
Calc: threaded
Comment 1 Mike Kaganski 2023-08-21 13:24:01 UTC 
I would assume that this information would be a kind of privacy risk - needlessly disclosing filenames. For linked cases it's reasonable / unavoidable, but doing an extra work to store this info where it's not needed, and is not expected by wast majority, would be strange.

On the other hand, if someone wants, they can always use the Format/Name, and put the filename (even with the path) there.

IMO, WONTFIX. But let's ask UX team.
Comment 2 Robert Pollak 2023-08-21 13:31:25 UTC 
I understand your concerns. Thanks for pointing out Format/Name. My current workaround is to store the source path in Properties/Hyperlink/Name.
Comment 3 Heiko Tietze 2023-08-21 14:36:03 UTC 
Duplicate of bug 133719 (and bug 124805).

*** This bug has been marked as a duplicate of bug 133719 ***