Bug 98861 - Exporting PPT to SVG puts text box contents on two lines and in the wrong order
Summary: Exporting PPT to SVG puts text box contents on two lines and in the wrong order
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: SVG-Save
  Show dependency treegraph
Reported: 2016-03-24 14:38 UTC by Elizabeth Holley
Modified: 2021-08-10 03:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Image Files (832.06 KB, application/zip)
2016-03-24 14:38 UTC, Elizabeth Holley

Note You need to log in before you can comment on or make changes to this bug.
Description Elizabeth Holley 2016-03-24 14:38:51 UTC
Created attachment 123810 [details]
Image Files


I am using Libre Office Version: on a Mac, running OSx 10.10.5. I use Libre Office to export to WMF, SVG and PCT files from PowerPoint. I am having two issues with my exported files:

1.	PCT files, text boxes appear with white background fills when placed on another colored object. The text box is formatted as no fill, shadow, lines, glow or soft edges. Another issue with the PCT file, is text boxes that have been turned on an angle. See Placed PCT File image attached.

2.	SVG Files, sometimes, not all the time text boxes that have been turned on an angle will convert the text box and display horizontally. See Placed SVG File & Placed SVG2 File images attached.

I am also including my original PowerPoint file. Any insight you can provide would be most appreciated.

Elizabeth Holley
Comment 1 Buovjaga 2016-04-03 14:32:00 UTC
Support for PCT exporting has been removed in LibreOffice 5.2 as obsolete (see bug 92925), so let's focus on SVG.

When I export from the PPT to SVG using LibreOffice 5.2, the only problem is that the Upper Entrance goes to two lines and now reads more like Entrance Upper. The angle remains the same.

The same thing happens with LibO 5.1.1 on OS X 10.11.4.

Arch Linux 64-bit, KDE Plasma 5
Build ID: 9b0069c2833313ba9fab91f45edd354ba334f94b
CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on April 3rd 2016
Comment 2 QA Administrators 2017-05-22 13:20:29 UTC Comment hidden (obsolete)
Comment 3 eisa01 2018-03-18 09:53:33 UTC
Still present

Build ID: 8e8dd8f320a3ff59ff8a16c1a7a867888ce80700
CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; 
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-03-13_23:59:29
Locale: en-US (en_US.UTF-8); Calc: group
Comment 4 QA Administrators 2019-06-21 02:52:07 UTC Comment hidden (obsolete)
Comment 5 eisa01 2019-08-10 20:37:07 UTC
This is still present

Build ID: 54028dc503fc08eb12e287919d5e2850cff05b73
CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2019-07-31_01:48:19
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 6 QA Administrators 2021-08-10 03:49:34 UTC
Dear Elizabeth Holley,

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