Description: LibreOffice should support Apple KeyNote file. But why doesn't it happen? Steps to Reproduce: 1. Open .key file in LibreOffice 2. Pick .key file to open 3. Error occured Actual Results: It should be supported .key file and automatically open in Impress Expected Results: But in fact it didn't happen. Reproducible: Always User Profile Reset: No Additional Info: I have made some document in Apple KeyNote via iCloud in Web Browser and pick-up some template, modified and save it as .key file. If I open in Impress, error occurred was happened. Note: If this bug has fixed later, there some many bugs that I have made cool transition and animation in every slide that doesn't supported or unavailable in Impress.
Created attachment 145837 [details] Sample Presentation.key Sample Apple KeyNote file that I have made
Created attachment 145838 [details] An Error Occured
Why? Do you know many peoples who received a .key presentation file and who were not able to open it because they do not use a computer under MacOS? I never read such issue on users mailing-lists. Please, could you explain why it is so important to make this effort? Best regards. JBF
Forget my previous comment. Well, I see that LO filepicker knows Apple Keynote file. So I guess that the error message comes from a filter which has not been updated after a change in a proprietary file format. I reproduce the error message. So set status to NEW. Best regards. JBF
I try to open this keynote file: https://bugs.documentfoundation.org/attachment.cgi?id=97347 attached to fixed bug 72030 and that does not work very well. Double-click on dekstop gives an error. Open from LO, works only if Apple Keynote filter is set first. The result is clearly not correct. @David Tardon: you may be interested by this bug report. Best regards. JBF
Also reproduced in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.10; Render: default; Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
*** This bug has been marked as a duplicate of bug 120707 ***