Download it now!
Bug 127275 - Wrong text format in PPTX SmartArt after saving in ODP format
Summary: Wrong text format in PPTX SmartArt after saving in ODP format
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.2.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: OOXML-SmartArt
  Show dependency tree / graph
 
Reported: 2019-09-02 07:50 UTC by Christian
Modified: 2019-09-18 11:56 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Testcase in PPTX format (38.81 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2019-09-02 07:50 UTC, Christian 		Details
destroyed formatting (178.86 KB, image/png)
2019-09-02 07:52 UTC, Christian 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian 2019-09-02 07:50:59 UTC 
Created attachment 153812 [details]
Testcase in PPTX format

The Text formatting is destroyed after a PPTX file is saved as .ODP and opened again.
It is fine after openeing the PPTX.

To reproduce:
* Open the attached PPTX
* save it as ODP.
* Close LO
* Open the saved ODP
Comment 1 Christian 2019-09-02 07:52:09 UTC 
Created attachment 153813 [details]
destroyed formatting

This is a screenshot of the destroyed formatting
Comment 2 Regina Henschel 2019-09-17 11:02:59 UTC 
LibreOffice tries hard to import "SmartArt" from MS Office documents. There has been recently a GSoC-project to improve it. But still a lot is missing. As workaround, you should convert the SmartArt-object to shapes in PowerPoint (It has an option for that), if that is possible for you. Then showing it in LibreOffice works.

I can confirm the error with
Version: 6.4.0.0.alpha0+ (x64)
Build ID: b5f4041ef04f6645cbd91d35f6231573e3042636
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: de-DE (en_US); UI-Language: en-US
Calc: CL
Comment 3 Xisco Faulí 2019-09-18 11:56:33 UTC 
@Grzegorz Araminowicz, I thought you might be interested in this issue...