Created attachment 135548 [details] Original Document Generating Corrupt SVG New to 5.4.0.3 SpreadSheet exports SVG images that are distorted Draw exports SVG images that are distorted Impress exports SVG images that won't open Writer doesn't export to SVG (not a feature?) For Draw and SpreadSheet, the previous "Fresh" version of LO exported perfect SVGs. This applies to Ubuntu 16.04 LO 5.4.0.3 To reproduce: 1) Open the attached file 2) Right-click on chart -> Export 3) Save as .svg
Unconfirmed on ubuntu 16.04 x64 with Version: 6.0.0.0.alpha0+ Build ID: 4e2b44860c2c304ea728c512b47ca07aaf1cd452 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-08-10_23:01:09 Locale: en-US (en_US.UTF-8); Calc: single
I cannot confirm with Version: 6.0.0.0.alpha0+ Build ID: b6e32d53ce9c98bfba517c40f53d40e97a091b0e CPU threads: 4; OS: Windows 6.1; UI render: default;
I can't reproduce it in Version: 6.0.0.0.alpha0+ Build ID: ef2e6260fad38e26c8591ea88ded348db618270d CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test?
Resetting User Profile - no affect Using java version "1.8.0_144" Java(TM) SE Runtime Environment (build 1.8.0_144-b01) Uninstalling Java (and fresh user profile) - no affect System Ubuntu 16.04 HP EliteBook 8440p
Created attachment 135653 [details] svg export of the chart Reproducible with LO 5.4.0 from Ubuntu PPA and with LO 5.4.2.0.0+ built at home under Ubuntu 16.04 x86-64. Setting as NEW Best regards. JBF
Indeed not reproducible in LO 6.0.0.0.alpha0+ built at home under Ubuntu 16.04 x86-64. Changed importance to high/major because an important feature is broken in current release. Best regards. JBF
Reproduceable under LibreOffice 5.4.0.3 System: Debian 4.12.6-1 (2017-08-12) x86_64 GNU/Linux The export is working as expected with LibreOffice 5.3.5.2 on the same machine.
Issue persists in LO 5.4.1.2 on Ubuntu 16.04. I suggest this issue be downgraded to trivial because export to pdf works fine and pdf easily converts to svg.
(In reply to Mathias Henry from comment #8) [...] > I suggest this issue be downgraded to trivial because export to pdf works > fine and pdf easily converts to svg. I strongly disagree because a regression is always a serious bug. The availability of a workaround does not change that. If a regression affects a function and is viewed as minor problem, that means you can remove this function. Best regards. JBF
Point well taken. I certainly prefer the svg option remain as it takes the user (me) directly to the desired result without any extra thinking.
Created attachment 136988 [details] Chart exported as SVG image from Calc in 5.3.2.2/5.4.2.2 on Ubuntu 16.04 (uploaded as PNG) This SVG export bug also present in 5.4.2.2 installed using DEBs on Ubuntu 16.04. On 5.3.2.2 works absolutely fine. Attaching examples. Checked and not due to corrupted user profile. Copying and pasting into Draw and exporting to SVG gives the same problem. Version: 5.4.2.2 Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-GB (en_GB.UTF-8); Calc: group
I tried to export an SVG file from Impress and the created file is empty (when viewing the SVG). Version: 6.0.0.0.alpha0+ Build ID: 9685532bc859167c1aa856c6f6792559904b8fb9 CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group
I can confirm a heavily distorted SVG-Export on Linux Mint 18 Mate 64bit using official LO 4.5.5.2 LibreOffice_5.4.4_Linux_x86-64_deb.tar.gz see attachment. (It is a Draw-Object in Writer created and exported with the extension ChordDiagrams https://extensions.libreoffice.org/extensions/chorddiagrams) It works correctly with master~2018-01-03_23.50.04_LibreOfficeDev_6.1.0.0.alpha0_Linux_x86-64_deb.tar.gz (Also No Problems on Windows 10 64bit with official LO 5.4.4)
Created attachment 138884 [details] Distorted_SVG_Exports
Created attachment 138933 [details] Simple 4-point filled polygon LO Draw project
Created attachment 138934 [details] Corrupt simple 4-point polygon LO Draw exported SVG
Created attachment 138935 [details] Corrected simple 4-point polygon LO Draw exported SVG Hi. Confirmed on openSUSE Tumbleweed, LO Version: 5.4.3.2 Build ID: 40m0(Build:2) I know what the problem is. I have looked deep in the LO source and cannot seem to find where the fault is. The attached Draw project exports a corrupted SVG, also attached. An example of a corrected SVG file is also attached. I think my correction is actually not quite the right point sequence but it works. Take a close look. Do you see what happens? It happens consistently with every project no matter how many points. The corrupted: -------------- <path style="fill:url(#gradient1)" d="M 483,0 L 1118,292 483,800 610,1308 483,800 Z"/> <path fill="none" stroke="rgb(0,0,0)" stroke-width="28" stroke-linejoin="round" d="M 483,0 L 1118,292 483,800 610,1308 483,800 Z"/> The corrected: -------------- <path style="fill:url(#gradient1)" d="M 610,800 L 483,292 1118,800 483,1308 610,800 Z"/> <path fill="none" stroke="rgb(0,0,0)" stroke-width="28" stroke-linejoin="round" d="M 610,800 L 483,292 1118,800 483,1308 610,800 Z"/> There are two ways to correct it: Shift each of the Y values to the RIGHT, or Shift each of the X values to the LEFT. (My corrected SVG file probably should have used the latter, not former.) After that, correct the M point with the last point value. See what I mean? Something in the exporter is mismatching the X and Y values, they are "out of phase" by one point so to speak. Possible to whip up a quick fix and release while we wait for 6.x? I need this to work. I get such fixed release packages in a few days here on openSUSE Tumbleweed. Thank you.
*** Bug 111394 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug is obsolete as it does not affect current versions of LibreOffice and therefore has no need for further attention. Status is being set in accordance to the instructions in the automated follow-up e-mail.