The following objects can be exported as vector objects from LibreOffice: - shapes - fontwork - formulas - QR codes / barcodes For example: - when exporting a selection from Draw, or exporting the whole document as PDF: these objects can be manipulated as vector objects. (e.g. in Inkscape.) - when exporting as XHTML: QR codes use SVG, and formulas use MathML (shapes and fontworks are missing, different issue). However, when saving an ODT or ODS as HTML, all these objects are converted to bitmaps. This means: - objects with bad resolution, especially for objects like QR codes, rendered unreadable (likely linked to bug 157323) - objects that can't be manipulated further (node-by-node, coloring of parts, breaking, modifying shapes...) SVG is now widespread and a standard that goes hand-in-hand with HTML on the web and elsewhere. We should use it instead of bitmap when possible. Steps: 1. Create ODS or ODT 2. Insert a shape, an OLE formula, a QR code and a fontwork (for fontwork, use a pure-vector option like "Snow") 3. File > Save as > HTML 4. Reload Result: all objects are bitmaps Expected: all objects are vector objects and can be further manipulated. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 91ca15e3f8ae13b22531745a634459a2d9b4596a CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same in OOo 3.3.
Ah, a more general "don't use Gif" request had been filed before in bug 115360. Let's keep this one as a more specific "use SVG for vector objects" request, and make it block the older report.
Created attachment 190831 [details] ODT with four vector-ish objects Document with the four types of objects suggested in the reproduction instructions.
I would call gratuitous rasterization a bug.
Dear Stéphane Guillou (stragu), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug