Created attachment 123529 [details] Example ODT document with 3d pie-chart created in Writer. Before saving in MS-Word. Create a file in LibreOffice, either a ODT or ODS, containing a PIE CHART with the 3D style. Open it in Word/Excel (specifically, PC version Office 2016) and make any change (just so it saves) and then save it (without changing the format). Open the updated file in LibreOffice again. The chart will appear corrupt so that the pie is no longer a pie but is insead a vertical line. Make no changes to the file. Close it and open in MSO again. The pie chart is rendered correctly. Confirmed this rendering on Windows PC and Linux versions of LibreOffice. It does not happen with the 2D pie chart. You can, in LibreOffice application, edit the corrupt chart to turn off the 3D effect and then turn it back on. This repairs the problem (until it's saved again in Excel!) I have attached an example file that was created in LibreOffice Writer. You can do the same thing in Calc. Just open it, in MSO, save it, and re-open in LibreOffice.
Created attachment 123530 [details] Copy of test file after saving in Microsoft Work (Windows PC Office 2016)
When corrupted, the "3D View" dialog reports X rotation of 90 degrees, Y rotation of 150 degrees , Z rotation of 90 degrees and perspective of 20%. When correctly rendered these values are -60, 0, 0, 5%. You can also fix the problem by editing the values on the "3D View" dialog, so it appears to be these values that get messed up by Excel. In fact it gets more interesting. The chart rendered by Excel is rotated differently to LibreOffice. Its "3D Rotation" dialog (side panel) reports X rotation of 90, Y rotation of 30, Z is zero and greyed out. Perspective is 5.8 degress. So I am guessing now but there must be TWO sets of data for the 3D arrangement of a pie. Also note that the effect doesn't happen on bar charts.
Could you also attach the .ODT saved from MSO 2016? I only have access to MSO 2013. I'm itching to run it through this validator, but you can do it yourself, if you want: https://odf-validator.rhcloud.com/
The Word file saved by MSO 2016 is the attachment already placed #123530. Apologies for the typo (it was saved with WORD, not work WORK). I ran the validator on it, it says it is non-compliant. But then it says that about the original odt, the output of which looks worse (but then I don't really know what I'm looking at...).
Apologies for my careless reading :) Yet, this really seems to be Microsoft's bug! I checked with developers on IRC and the original ODT not validating is not dangerous, but quite normal. So if it breaks after a dip into MSO, we can blame MSO.
Just curious how things like this are handled. Clearly it is a MS issue but is there any path for raising such things as these? I ask because, regardless of blame, when a document doesn't port bidirectionally between Microsoft and LibreOffice the perception is that "it doesn't work as well as office" and the end-users/decision makers will throw LO out with the bathwater. The cynic in me would say that Microsoft fixing things like this is not in Microsoft's best interests...
I found this: https://support.office.com/en-us/article/How-do-I-give-feedback-2b102d44-b43f-4dd2-9ff4-23cf144cfb11
Yeah, I know. It's a symlink to /dev/null most likely though :) Just wondered if there was any internal liaison between the two. I guess not.
Well, MS is present in some meetings: http://odfplugfest.org/2015-thehague/programme/ Boris Devouge (Microsoft, UK) Microsoft Office - What's new in ODF since London 2014