Please add a warning when inserting .svg files if the current document format will convert it to bitmap. At first I thought I was running to bug 42092, but after trying to isolate the problem to report a new bug for Presentation, I discovered it was only a problem if the current file format is a ".pptx" format. It was not obvious what was going on, the export to PDF option was producing very ugly results, areas of the .svg were covered by black boxes I'm not sure if this is a limitation of .pptx but consider converting to the .svg to some other scalable format (perhaps enhanced meta file?) that would work for .pptx.
@Nick, *, The OOXML .pptx output is not native to LibreOffice. Do you have any better results if working with the native ODF formats. Use ODG for importing the .SVG and then placing that image into a ODP presentation? The .SVG formatting is retained 100% going into ODG. And, it has good fidelity in its vector data format on export to PDF from the Draw component. Also, when the Draw image object is placed into the Presentation it remains a vector graphic at full resolution. But, it does seem a bit degraded when exporting from Presentation to PDF--it is still a vector graphic, but the vertices are no longer identical. I think that is a pstoedit issue in the PDF filter.
Yes, it works fine when the file format is open-document. PDF output looks super, and I confirmed the imported .svg is saved as a .svg inside of the .odp. I'm suggesting a warning dialog if the file format is not open-document.
I imported a SVG into a PPTX, and in the file content I have the SVG file. Not transformed to bitmap. Could you retest? Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b7d2a9c824aca1a4dfd1b857a3620e73ade6bc0d CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
If I insert an svg image into a pptx and open it in PowerPoint, the image looks blurry. I am not sure if the content is svg, but at least there is a pixmap preview.
Dear Nick, 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: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Nick, 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 Warm Regards, QA Team MassPing-NeedInfo-FollowUp