Bug 95503 - FILESAVE: Presentations with motion paths saved as PPTX can't be opened in PowerPoint
Summary: FILESAVE: Presentations with motion paths saved as PPTX can't be opened in Po...
Status: RESOLVED DUPLICATE of bug 111518
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.1.0.0.alpha1
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: interoperability
Keywords: filter:pptx
Depends on:
Blocks:
 
Reported: 2015-11-01 17:26 UTC by avkaplmkt
Modified: 2017-08-09 14:24 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Original ODP, text box on first slide has motion path animation. (69.74 KB, application/vnd.oasis.opendocument.presentation)
2015-11-01 17:26 UTC, avkaplmkt
Details
Original ODP saved as PPTX, PowerPoint 2010/2011/2013 say the PPTX is corrupted. (87.90 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2015-11-01 17:27 UTC, avkaplmkt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description avkaplmkt 2015-11-01 17:26:23 UTC
Created attachment 120166 [details]
Original ODP, text box on first slide has motion path animation.

Hello,

When I add a motion path animation to an object in Impress and save it as Powerpoint 2007-2013 XML .pptx format, Powerpoint 2010 (Win)/2011 (Mac)/2013 (Win) complains that the file is corrupted and fails to repair it. This is a show stopper/major blocker for me, hope it gets fixed!!
Comment 1 avkaplmkt 2015-11-01 17:27:56 UTC
Created attachment 120167 [details]
Original ODP saved as PPTX, PowerPoint 2010/2011/2013 say the PPTX is corrupted.
Comment 2 avkaplmkt 2015-11-01 17:28:51 UTC
I tried saving the PPTX file in Windows, Mac OS X, and Linux versions of LibreOffice, in all cases all PowerPoint versions I tried say the PPTX is corrupted... :(
Comment 3 avkaplmkt 2015-11-01 17:30:58 UTC
I also tested this in Impress 5.0.x, same problems.
Comment 4 V Stuart Foote 2015-11-01 19:52:34 UTC
So how do things fare if instead of .pptx your pass MS Office the .odp?

Its MS's mess, let them deal with importing--rather than exporting to OOXML.

(Yes I know sometime you have to prepare .pptx/.ppt to exchange, but how often is that really necessary--especially now that MS has fairly complete support of ODF 1.2 formats?)
Comment 5 V Stuart Foote 2015-11-01 20:10:24 UTC
Ok for what it is worth, the ODF attachment 120166 [details] .odp opens and the text path renders correctly in MS Office 2007 SP3 Powerpoint. 

Saved from MS Office 2007 to OOXML  the OOXML .pptx opens and closes with no further complaint.
Comment 6 avkaplmkt 2015-11-01 21:16:38 UTC
(In reply to V Stuart Foote from comment #4)
> So how do things fare if instead of .pptx your pass MS Office the .odp?
> 
> Its MS's mess, let them deal with importing--rather than exporting to OOXML.
> 
> (Yes I know sometime you have to prepare .pptx/.ppt to exchange, but how
> often is that really necessary--especially now that MS has fairly complete
> support of ODF 1.2 formats?)

Thanks for your quick reply.

The .odp opens messed up in so many ways (not just the motion path) in Microsoft Office (2013 and below) it just doesn't work at all.

Actually, I have to export to .pptx almost every day for Microsoft PowerPoint (most commonly 2010 on Windows, but also 2008/2011 on Mac OS X, and 2013 on Windows), and as I noted above, ODF support in Office is still a mess at least for .odp. In addition, the Mac versions of PowerPoint can't read .odp files. So this bug is pretty major for me.

And since interoperability with Microsoft Office is touted as a big feature of LibreOffice, I think it is still critical to make sure exporting to .pptx (and .docx and .xlsx for that matter) works without a hitch. Yes I realise Microsoft's own implementation of .pptx changes between every version of PowerPoint, but the point stays the same.

Glad to hear that PowerPoint 2007 opens the .odp and renders the path. But does everything look exactly the same as in Impress?
Comment 7 V Stuart Foote 2015-11-02 01:51:37 UTC
(In reply to avkaplmkt from comment #6)
> Glad to hear that PowerPoint 2007 opens the .odp and renders the path. But
> does everything look exactly the same as in Impress?

Only visual glitch is the color of the text box object--black instead of white, easily adjusted. But that is just for this simple two slide test file. Understand there could be a lot of thrash between ODF and OOXML on a real world presentation.

Still beleive the better choice is to work in ODF and avoid "features" that don't translate between the two--either ODF to MS Office or OOXML to LibreOffice. And as with Writer--for high fidelity "exchange" send PDF or XPS print output.

But setting NEW as it is a valid issue with OOXML export filters.
Comment 8 avkaplmkt 2015-11-02 08:55:22 UTC
(In reply to V Stuart Foote from comment #7)
> (In reply to avkaplmkt from comment #6)
> > Glad to hear that PowerPoint 2007 opens the .odp and renders the path. But
> > does everything look exactly the same as in Impress?
> 
> Only visual glitch is the color of the text box object--black instead of
> white, easily adjusted. But that is just for this simple two slide test
> file. Understand there could be a lot of thrash between ODF and OOXML on a
> real world presentation.
> 
> Still beleive the better choice is to work in ODF and avoid "features" that
> don't translate between the two--either ODF to MS Office or OOXML to
> LibreOffice. And as with Writer--for high fidelity "exchange" send PDF or
> XPS print output.
> 
> But setting NEW as it is a valid issue with OOXML export filters.

Thanks for marking this bug as NEW.

Regarding to the "only" visual glitch, like you suggested there are many many more problems when opening ODP in PowerPoint, and exporting to PPTX also has many problems. The truth is real world demands very often require users export to PPTX (and DOCX and XLSX) for various reasons, and getting the interoperability to work is so important for adoption of LibreOffice.

For high fidelity, *using PDF is wholly insufficient* simply because so many things (such as motion paths, transitions, etc.) are not saved as PDF, and PDFs are generally not editable. Hope someone fixes these problems soon! And thanks to all the developers for bringing LibreOffice this far.
Comment 9 Robinson Tryon (qubit) 2015-12-07 16:29:14 UTC Comment hidden (obsolete)
Comment 10 Xisco Faulí 2016-12-20 00:04:58 UTC
Analyzing the error with Open XML SDK 2.5 it's the same as in bug 104784 where it's described more in detail. Closing this as a dupe of that one

*** This bug has been marked as a duplicate of bug 104784 ***
Comment 11 Xisco Faulí 2017-08-09 14:23:40 UTC
Issue fixed by af4602e558431bcdf51d0f15e7e400adcd142738.
Closing as RESOLVED DUPLICATED OF bug 111518
Comment 12 Xisco Faulí 2017-08-09 14:24:59 UTC

*** This bug has been marked as a duplicate of bug 111518 ***