Description: I created an svg in Inkscape. It is a path with an end marker. This end marker is #ArrowWideRounded. So in total I have made an arrow in svg. When copying the file to Writer or Impress the Arrow-End (in svg-slang: marker-end) doesn't show up. When using a different marker-end such as #ArrowTriangleStylized it shows up and works. The #ArrowWideRounded also doesn't work at marker-start or marker-mid. #ArrowTriangleStylized works in all of them Here is a link to my svg and also the odt and odp. I have also exported pdfs because that also doesn't work: https://drive.google.com/drive/folders/1jjlRmzWWS9VXb6HgAV3w0mulLXd3QmVQ The svg is called "bug.svg" Steps to Reproduce: 1. Copy the svg into Writer/Impress 2. See that the arrow-ends on the top should-be-arrow don't show up 3. Export a pdf 4. See that the arrow-ends on the top should-be-arrow don't show up Actual Results: The top arrow is only a line. The bottom arrow has three arrow-ends. Expected Results: The three arrow ends of the top arrow should show up like on the bottom arrow, but with a different design, like how they do in Inkscape. Reproducible: Always User Profile Reset: No Additional Info: I have also opened the .odt and .odp files with an Archive Manager. When looking at the internally stored .svg file and opening it with Inkscape the top arrow is correct. That suggest only the rendering of LibreOffice is wrong. But when opening the exported PDFs in Inkscape the top arrow is just a line, that suggest that on export the marker-ends of the top arrow get lost.
Created attachment 193868 [details] The .svg file where the top arrow doesn't get displayed correctly
Reproducible Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded and Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ea43cbbb7371a743f470d949762a0e92f196e652 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded even worse with: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ea43cbbb7371a743f470d949762a0e92f196e652 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Also reproduced in Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 229123ccc6f90ebf66b3e659bebbd53f8a9bdd3a CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: fr-FR (es_ES.UTF-8); UI: en-US Calc: threaded
This is related to a661f9a2e0a05de1705a8e9d930c148a1416be29
Created attachment 193893 [details] LO24.2 & Inkscape 1.3.2 comparison Reproduced in: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: pl-PL (pl_PL); UI: pl-PL Calc: CL threaded
The problem is "stroke:context-stroke", if it's replaced by "stroke:#000000" then the markers are displayed. Closing as DUPLICATED of bug 155651 *** This bug has been marked as a duplicate of bug 155651 ***