Created attachment 94506 [details] Chart showing issue with data label This bug was tested LibreOffice v4.3 running in windows 7. It appears that LibreOffice loses formatting when importing MS .xlsx files with charts. I have attached an example. Steps to reproduce the bug: 1. Open Demo-Hayden-Management-v2-chart.xlsx document in calc 2. Open Demo-Hayden-Management-v2-chart.xlsx document in Excel 2007/skydrive 3. Compare the documents. Note: The first data label of 2nd column (250) is displayed on the bottom of the chart.
Created attachment 94510 [details] Recreated the data labels in Excel 2007 I believe this chart was original created in Office 2013. To try to narrow down the issue, I redid data label in Excel 2007. This new chart opens correctly in LO Calc. Attached is the updated file. If you unzip it and run a diff of \xl\charts\chart1.xml you’ll see: </a:schemeClr></a:solidFill></c:spPr><c:dLbls><c:dLbl><c:idx val="0"/><c:layout><c:manualLayout><c:x val="0"/><c:y val="1.1990407673860906E-2"/></c:manualLayout></c:layout><c:showVal val="1"/><c:extLst><c:ext uri="{CE6537A1-D6FC-4f65-9D91-7224C49458BB}" xmlns:c15="http://schemas.microsoft.com/office/drawing/2012/chart"><c15:layout/></c:ext></c:extLst></c:dLbl><c:dLbl><c:idx val="3"/><c:layout> Are some new OOXML codes confusing the importer? Can any OOXML gurus shed some light on this issue?
Reproducible tested Windows 8.1 Version: 4.3.0.0.alpha1+ Build ID: 145f2e970f46a3a3e5456b122d71f17c3abe878f TinderBox: Win-x86@42, Branch:master, Time: 2014-04-26_23:32:36 Kind regards, Joren
This has nothing to do with OOXML at all. This is part of our manual label placement. So this requires reworking the automatic label placement code. You can get the same problem with a freshly generated document. I'm not going to look into this any deeper as these placement codes are just a huge pain.
Still rendered incorrectly in 5.2.0.0.alpha1+ Build ID: a5a71cea62ac3041006c5e9815ae2317999639ac
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Still an issue with: Version: 5.5.0.0.alpha0+ (x64) Build ID: 20d04d6938a104124ac06271f17978a290cccf6c
Verified FIXED in Version: 6.1.0.0.alpha0+ Build ID: 20e5f64215853bdd32c5f16394ba7f2f36745904 Thanks Szymon Kłos *** This bug has been marked as a duplicate of bug 114821 ***