The attached PPTX has a dashed line.
The size of the PDF exported from impress is 21KB, x10 compared to PDF exported from PowerPoint.
When exported to SVG the line is converted to many small path elements and the file size is 726KB.
Steps to Reproduce:
1. Open the attached line.pptx file in Impress
2. Export to PDF and check the file size.
3. Export to SVG and check the file size.
PDF file size is 21KB.
SVG file size is 726KB.
SVG has many small path elements.
PDF file size should be 3KB.
SVG file size should be few KBs.
SVG should have a single dashed line element.
User Profile Reset: No
Created attachment 146033 [details]
PPTX with a dashed line
Created attachment 146034 [details]
PDF exported from impress
Created attachment 146035 [details]
SVG exported from Impress
Created attachment 146036 [details]
PDF exported from PowerPoint 2013
please create different bugs for different problems with PPTX->PDF and PPTX->SVG
I assumed the SVG and PDF are related because both are vector formats.
Please ignore the SVG for now and let's focus on the PDF.
When I open the PDF exported from Impress in Inkscape I can see many small rectangles. The PDF exported from PowerPoint has a single element.
Can you attach result of PDF export from MS Power Point?
'PDF exported from PowerPoint 2013' is in the attachment list:
Let's use this bug to track the SVG problem only
Build ID: f420aa3e027e04e49b7031ebf0613debcaab2ea0
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.15; Render: default;
the size is 334 kbs...
This seems to have begun at the below commit.
Adding Cc: to Marco Cecchetti ; Could you possibly take a look at this one?
ec0e5b057dc3cbbda20e94e608eb7005432d6b68 is the first bad commit
Author: Jenkins Build User <firstname.lastname@example.org>
Date: Thu Dec 7 10:57:55 2017 +0100
author Marco Cecchetti <email@example.com> 2015-12-02 17:57:57 +0100
committer Andras Timar <firstname.lastname@example.org> 2015-12-09 19:38:19 +0000
commit 154521777f8c551f10ffbe414891df9d2a529ae3 (patch)
parent 689962feae2054f965a7378c3408b0ccfad2bbd5 (diff)
svg export: no more an experimental feature
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!
471 kb in
Version: 18.104.22.168.alpha1+ (x64) / LibreOffice Community
Build ID: 58b0c95ad50139a62bddb348d10f94053c09cd5b
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
so still repro
Exported into pdf and svg formats,line element was same in both formats. pdf size: 1.56kb and svg size:482kb.So still reproducable in LO 22.214.171.124 under Windows 10(x64).
Version: 126.96.36.199 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ta-IN (en_IN); UI: en-US
I suppose a solution to avoid multiple paths could be to support stroke-dasharray on SVG export: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/stroke-dasharray
But in this case, the exported SVG is mainly made up of an ECMAScript from line 161 to line 16704.
This is not specific to PPTX. One can export an ODP file to SVG, the same script will be included.
Version: 188.8.131.52.alpha0+ (X86_64) / LibreOffice Community
Build ID: ec60d354359067f8c5c686ef2239ee705916de43
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US