Created attachment 75376 [details] Screenshot of the master page Description of problem: When attempting to export a presentation to the SVG format, the result differs from the original (color and font) in 3.6. But when trying to perform this operation on this LO 4.0 closes unexpectedly. I noticed that when exporting to that format, follows the guidelines of the master page and it looks like the current slide (attached ODP, PDF and SVG test presentation, also attached screenshot where it shows color master page). Version-Release number of selected component: Fedora 18 (Spherical Cow) 32-bit GNOME 3.6.2 LO version 3.6.5.2 (Build ID: 3.6.5.2-2.fc18) LO version 4.0.1.0+ (Build ID: a5acd33bc54cbc00f2194c923641fbd0ab45d80) How reproducible: 1. Open a presentation (ODP) with LO Impress 2. Open file menu and select "Export" 3. Select and export SVG document Actual results: In LO 3.6, the export is performed without problems (current slide), but the results differ from the image of the slide. In LO 4.0 to try to do this, the program closes unexpectedly. Expected results: That the export performance as faithful to the slide is displayed in LO Impress Additional info: I do not know the method of export to SVG using LO, however I have read that format and your chances are much broader. With regard to the particular case, it would be ideal to embed the font used (or transform it into strokes). I realized the mistake trying to pass some presentations (ODP) to SVG format and then create presentations Prezi style with Inkscape and Sozi plugin.
Created attachment 75377 [details] ZIP Archive with screenshots Attachment in the ZIP file - Presentation ODP test - Presentation in PDF - Picture exported in SVG format - Image Capture (error when exporting) as 4.0 on Windows I can verify that there is a similar problem when exporting SVG format in LO 4.0 under Windows. Instead of closing as Linux, Windows reports an error writing. Windows 7 PRO 32-bit LO Version 4.0.0.3 (ID de compilación: 7545bee9c2a0782548772a21bc84a9dcc583b89) Thanks
partly reproducible with LO 4.0.1.2 (Win7 Home, 64bit) The export functions works with Win7 without error message. @Bastián: Does this issue still persists for you with the latest release of LO? But, what I can confirm is that the exported slide is in yellow, while the presentation is in blue, which seems to be related to the Master Page settings. @Radek: Could this maybe be something for you?
(In reply to comment #2) > The export functions works with Win7 without error message. > @Bastián: Does this issue still persists for you with the latest release of > LO? Indeed follow the same drawbacks in LO impress both Linux (4.0.1.2) and Windows (Versión 4.0.1.2 84102822e3d61eb989ddd325abf1ac077904985). Moreover, you can add some extra difficulty (see inkscape logo in attachment).
Created attachment 77389 [details] difficulties with SVG exported LO impress Beware inkscape logo and typography.
The problem persists in version libreoffice (Versión: 4.1.0.1 - Id. de compilación: 4.1.0.1-8.fc19). I do not see the error message, but the export does not work properly. → The background color does not appear in the exported version (usually export only typography and images on a transparent background) → You can only export a slide. When exporting multiple slides, they appear superimposed on a single image. Would it be possible to improve export in SVG format?. I mean something similar to what happens to export to PDF (page) or grid view (single page) or files with layers (1 layer per slide). The idea is to reuse the SVG format display and use other tools (such as sozi with Inkscape plugin and make a Prezi stylish presentation).
I can confirm same results as comment 1 with LO 3.6.6.2 (Ubuntu 12.04 32bit). Export to PDF & SVG produce different background color. Result on comment 4 not occured. If that occur with 4.0.1, I think that issue should be reported on different bug report.
Tested on LO 4.0.4.2 (Win7 32bit), I can reproduce behavior on comment 4. @Bastián, I would suggest to open new bug report following this regression problem.
(In reply to comment #7) > @Bastián, I would suggest to open new bug report following this regression > problem. Hi @ign_christian Do not quite understand you need. Do I have to open a new bug report the problem? or do you just need to open another bug report specifying the problem of comment 4? thanks
> Do I have to open a new bug report the problem? Yes please :) Then you could link this bug report to the new report in section "See Also" Hope that will help dev to track these issues
Hi Bastián, I think issue on comment 4 is covered in Bug 60757. Please take a look at that.
Sorry..not related. I forgot that's about export to svg :)
Summary amended to make it clearer what the problem reported in this bug is. The particular issue is as indicated in comment #2. The master page has a background color of "Chart 10" (#ff950e) i.e., in styles.xml: > <style:style style:name="Default-background" style:family="presentation"> > <style:graphic-properties draw:stroke="none" draw:fill="solid" draw:fill-color="#ff950e" draw:fill-image-width="0cm" draw:fill-image-height="0cm"/> > <style:text-properties style:letter-kerning="true"/></style:style> ... while the slide in the presentation (attached in comment #1) uses "Sea blue" (#0066cc) i.e., in content.xml: > <style:style style:name="dp1" style:family="drawing-page"> > <style:drawing-page-properties presentation:background-visible="true" presentation:background-objects-visible="true" draw:fill="solid" draw:fill-color="#0066cc" draw:fill-image-width="0cm" draw:fill-image-height="0cm" presentation:display-footer="true" presentation:display-page-number="true" presentation:display-date-time="true"/> > </style:style> Export to SVG results in the graphic using "Chart 10" rather than "Sea blue". Any use of Format > Page... > Background tab on a slide appears to be ignored i.e., in this case if there was no associated master page then no page background color would be exported.
Behaviour reported in comment #12 has been tested under Ubuntu 10.04 running: - v3.3.0.4 OOO330m19 Build: 6 - v3.4.6.2 OOO340m1 Build: 602 - v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b - v3.6.7.2 Build ID: e183d5b - v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 - v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a In all cases the background colour of the master page is written out to the SVG rather than the background colour of the slide (direct formatting). Version set to Inherited From OOo.
*** Bug 66900 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 on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
(In reply to Bastián Díaz from comment #1) > Created attachment 75377 [details] > ZIP Archive with screenshots Now the svg export is even more broken: the mountaintop turns all square-y. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 437210d58f32177ef1829d704f7f4d2f1bbfbfdd TinderBox: Win-x86@39, Branch:master, Time: 2015-06-18_07:21:56 Locale: fi-FI (fi_FI)
** 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 (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
The problem still exists in Version: 6.1.0.0.alpha0+ (x64) Build ID: 401a3d2336bf46b38235c498ff86ff675d0de759 CPU threads: 8; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-28_00:13:08 Locale: de-DE (de_DE); Calc: CL
** 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
still repro with file ODP from attach in Version: 6.3.0.0.alpha0+ Build ID: ba17d2e3c1acd571a4faa7e31ef97a2ec71591bd CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-12-10_01:14:49 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Dear Bastián Díaz, 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://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
Dear Bastián Díaz, 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
Reproduced in: Version: 6.2.0.3 Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded Fixed in: Version: 6.3.6.2 Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded It was fixed for bug 115549, marking as duplicate. *** This bug has been marked as a duplicate of bug 115549 ***