Created attachment 141481 [details]
a "project folder", containing a document with an image insterted (as relative URL), from an "image folder" also contained in the "project folder" -- for illustration puroposes
when inserting an image into a document, I totally miss the option to select what type of path, relative, absolute, or perhaps project-folder-relative... which, as a matter of fact, MS word had even some 10 years ago, AFAIR...
the problem now is that I set the way of handling image urls... "centrally",
say, I set it to relative, but for the appearance it will look (it will be corrected, auto-replaced) absolute... an absolute file path...
which makes two things impossible:
#1 tell if that URL is relative or absolute.. (huge problem)
#2 select the "text", "select/all" and "copy" and "paste" it to a WYSIWYG HTML editor such as tynimca or Trumbowyg..
_ _ _ _ _ _ _ why this enhancement should be implemented? _ _ _ _ _ _
IMO, to make it possible to choose from "ABSOLUTE / RELATIVE / Relative to project folder" is an urgent requirement, but this is also the beginning of a new approach to handling documents... with focus on flexibly and reliably handling inserted media...
The handling of inserted media -- I'm no expert -- seems to me a kind of task which video editors, namely, KDENLIVE performs at master level...
Linked media should not be treated as something extra or extraordinary, but as the most basic and general thing, like typing "hello" -- of course, you know all about it, way more than I do..
I am practically certain that we all agree that today, when people write books, collaborate on projects, use cloud, and when images are key thing everywhere...
the task of inserting images into a document in a transparent and reliable, and systematically controllable way is a minimum requirement...
thank you for your work, thank you for LibO, especially for Writer ! :)
PS: I like "Bug report 111957" by Mike Kaganski
PPS: the attachment is basically for illustration purposes :)
Can you explain very briefly, what your proposal brings on top of bug 111957?
(In reply to Buovjaga from comment #1)
> Can you explain very briefly, what your proposal brings on top of bug 111957?
Dear peter josvai,
Could you please answer the question above in order to help us triage this issue?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the question has been answered
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker