https://bugs.documentfoundation.org/show_bug.cgi?id=163391
Regina Henschel <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |136406 --- Comment #2 from Regina Henschel <[email protected]> --- I have tested it with a MS Office 365. I have created a document with linked image and saved it in doc-format. I have opened the created doc-file in MS Office 365 and verified in File > Info > 'Edit Links to Files' that the image is indeed linked. Then I save the file to docx-format in keeping compatibility. Then I have opened the created doc-file in MS Office 365 again and now saved it without keeping compatibility. I have opened the created files in LibreOffice 24.8. The doc-file shows the image. The docx-file without compatibility shows the image. The docx-file with compatibility does not import the image. The not-compatible docx file uses as pic:blipFill element in an a:graphic element and writes the target as absolute URL in the r:id element. The compatible docx file has the image in a w:pict element with VML child elements v:shapetype, v:shape and v:imagedata. The compatible docx file has an additional information about the image in a w:instrText element. But that seems to be unrelated. After removing the according run and the related runs with w:fldChar element, the document still opens fine in Word. So removing does not harm. The image is still missing in LibreOffice after these removals. Method getFragmentPathFromRelId(...) returns an empty string in case of an external target and thus mrTypeModel.moGraphicPath has an empty string in case VML_TOKEN(imagedata) in https://opengrok.libreoffice.org/xref/core/oox/source/vml/vmlshapecontext.cxx. So implementation of external images is totally missing in case of VML. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136406 [Bug 136406] [META] OOXML VML shape related issues -- You are receiving this mail because: You are the assignee for the bug.
