Created attachment 104118 [details]
What gets mangled …
The attached document gets mangled when it exports PDF (attached).
Created attachment 104119 [details]
The SVG document that was included
Created attachment 104120 [details]
The mangled PDF
NOTE: The mangling doesn’t happen if I don’t attach the SVG.
The SVG originates from Finale 2014c, btw.
Also, I get transparency errors when I export to PDF.
Also, if I use the OS’s PDF export feature (“Save as PDF” in the print dialogue), it errors without saving a new file.
Created attachment 104121 [details]
PDF export from LibO 4.2.6
Thank you for submitting the bug. I tested the document on Linux with 4.2.6, 4.3.1 and master and it wasnt a problem. Its possible its not showing for me as i dont have the 'GoudyOlSt BT' font installed.
I have forward this onto our QA mac team to have a look at.
Trying to confirm this bug, the following happened:
* open LO 188.8.131.52 or 184.108.40.206a0+
* Insert > Image > From File
* select SVG (second attachment from this bug)
Result: the svg get's displayed wrong (no notes, but a "w" and a line.
Well, at least when exporting to PDF, I see the same.
Felipe: could you try with LO 220.127.116.11 and see, if you get identical results?
I'm setting this to NEW since either way we have a bug at hand. Either the svg is not displayed correctly (18.104.22.168) or the svg is not correctly exported (4.2.x) the latter which I didn't test and couldn't confirm with 22.214.171.124.
Image seems to display and export just fine for me on OSX 10.9.4
Build ID: a0b89100be8ccc2b60d08d7e3819cd247a6042b0
that is my master build
I used the posted ODT file for testing.
SVG image import is known to be buggy, dependent on the svg image properties and the LO module code importing the svg, as far as I understand.
Also seems fine on LO 4242, am I perhaps missing something ? What is not being displayed correctly ?
Ah, now I see the problem. I downloaded the svg file and then opened it, by default in Safari, which shows the notes on the stave> Firefox, however, shows the same things as LO, hence my confusion.
Confirming that LO incorrectly displays svg file, hence export to pdf also wrong.
fwiw, the svg is also correctly displayed in Google Chrome
** 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 on a currently supported version of LibreOffice (126.96.36.199 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
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)
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: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
OS X 10.10.5
LO Version: 188.8.131.52.alpha1+
Build ID: 50f2c712c46c66264279ab3b61888e491a4d8dca
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2015-09-04_04:59:19
Locale: de-DE (de.UTF-8)
Attaching PDF in non broken form.
Created attachment 118407 [details]
non broken PDF
Does NOT work for me.
(Steve, your latest attachment won’t download to me … something about an incorrect MIME type.)
The same reproduction steps as before yield the same bug, on the same MacOS and LO version that you cited.
Felipe, thanks for the feedback. By now I re-read the entire bug and am unsure what this bug is about. From what I read there are two issues here:
1. PDF export mangles the document (we need exact a) b) comparison of what the document looked like in LO and what is broken in the exported PDF. Currently we do not know what we are looking for. Please be as specific as possible.
2. SVG not displayed correctly in LO: Again, I am not sure what we are looking for. I am seeing a note staff with a "W" on it. Is that the expected result or not? If not, again a) b) would be important to have.
Regarding the SVG I did open the file in Chromium, Firefox and Safari: Only Safari did show a staff with notes in it. Firefox, Chromium (and LO) did display a staff with a "W" in it.
To move things into a useful direction I am tempted to suggest to create new bugs - one for each problem (that's the general policy anyhow). Then again, if Firefox and Chromium fail to properly display the SVG, LO has some great company and I'd want some dev input about this specific SVG file.
(In reply to steve -_- from comment #17)
> Felipe, thanks for the feedback. By now I re-read the entire bug and am
> unsure what this bug is about. From what I read there are two issues here:
See my comment 11
The problem is the incorrect SVG import (and display in Writer), which logically leads to an incorrect PDF on export.
The stave should show music notes and not the "W" symbol.
Open the SVG in Safari and you will see the difference.
Setting to NEW as this was never fixed.
Note that the PDF isn't as mangled in LO 5012 as Felipe's attachment, only the export of the incorrectly imported SVG is of course wrong.
Correcting title to reflect this.
It would probably be better to check whether this isn't a duplicate of other, related SVG import bugs.
Alex, agreed. I still wonder though why Firefox and Chromium (both browsers with a lot more users than safari) both incorrectly show the music staff svg without the notes but with the wrong "w".
The PDF itself exports fine for me now, but the SVG is not rendered correctly
I've created bug 113501 for the SVG rendering, as that's a separate issue
Build ID: 15dce20e8b97dbd0179f01910ca4d0027e80ff4e
CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default;
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-10-20_06:46:46
Locale: en-US (en_US.UTF-8); Calc: group