until 4.2, when including images in html type documents with writer/web, the document would contain the pathes to the image files. Apparently because of bug 63211 such image files are now always converted and embedded, though the initial response in 63211 was that there was no bug, and that the need for embedding images should be handled as a feature request. The addition of the feature of embedding images should have maintained the possibility for traditional referencing by adding a configurable Option. One of the consequences of embedding images is that the html source can not be edited; when doing so by selecting Display- HTML Source, making a modification and saving the file, will result in a corrupted file as the embedded image will be split. This alone proves already the existence of a bug. External editors (bluefish, kwrite) will not accept modification because of excessive line length. The need for the possibility of editing html files in source is evident as the wysiwyg mode is fine but restricted, and does not allow to add some javascript for instance.
as writer/web has become unexploitable since the first upgrade in april (three major problems have been corrected, but this one still remains unsolved), and as I do no longer want to boot a partition with an old version of libreoffice to edit web pages in wysiwyg mode, I made the drastic move to openoffice (with success). For 20 years it has been a simple fact that I could edit html pages with an ordinary text editor (usually vi but now also kwrite) but I have not succeeded in finding an editor for editing at source level the html produced by writer/web of libreoffice 4.2 when an image is embedded. I wish that more capable contributors may be found for libreoffice as to satisfy reasonable user requirements and to allow me to become a libreoffice user again.
Since the resolution to bug 63211, images have been automatically internalised into HTML documents regardless of how they are inserted (even if inserted as a reference manually by editing the source) While this is useful for some use cases, it's a hindrance in others. Internalising the images should be optional.
Ah, and there's a duplicate *** This bug has been marked as a duplicate of bug 48887 ***