https://bugs.documentfoundation.org/show_bug.cgi?id=133719
Heiko Tietze <heiko.tietze@documentfoundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
|.freedesktop.org |tion.org
Status|UNCONFIRMED |NEW
Keywords|needsUXEval |
--- Comment #7 from Heiko Tietze <heiko.tietze@documentfoundation.org> ---
We discussed this topic in the design meeting. Storing the path is a privacy
issue but we could store the name in Image Properties > Options > Name. The
benefit besides better transparency what image is used, the image name is
listed at the Navigator and any <Foo> is better than just Image1.
If the image name exists (source from different directories) it should extended
by *_1 to _n.
It sounds also like a good plan, to delete these information if personal data
is not saved. However, we didn't figure the actual option- the one under File >
Properties > General is just about user's full name. Regina, what exactly do
you mean?
But to deal with the issue in general, having companies in mind, we suggest to
add an expert option that allows to disable the usage of file names (and keeps
the current behavior).
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 133719] Image Properties should display original filename and path by default · bugzilla-daemon
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.