Created attachment 121281 [details] .ods file with chart to illustrate the issue Round-tripping an MS Office file with a chart or saving a LibreOffice file to OOXML with strip away the data point color. Steps to reproduce: 1. In Writer or Calc, create a chart. 2. Edit Chart 3. Format Data Point -> Area -> Color 4. Select a different color than the series 5. Save as DOCX/XLSX 6. Close and reopen
Created attachment 121282 [details] a .docx file with chart to roundtrip
Created attachment 121283 [details] a .xlsx file with chart to roundtrip
Created attachment 121286 [details] Even simpler xlsx example that uses RGB color The roundtripped file can be fixed by adding back the following code to xl\charts\chart1.xml <c:idx val="0"/><c:spPr><a:solidFill><a:srgbClr val="FF0000"/></a:solidFill><a:ln><a:noFill/></a:ln><a:effectLst/></c:spPr></c:dPt> attachment 121283 [details] uses scheme colors and fixed by adding back the following code to xl\charts\chart1.xml <a:solidFill><a:schemeClr val="bg1"/></a:solidFill><a:ln w="9525" cap="flat" cmpd="sng" algn="ctr"><a:solidFill><a:schemeClr val="tx1"><a:lumMod val="15000"/><a:lumOff val="85000"/></a:schemeClr></a:solidFill><a:round/></a:ln><a:effectLst/>
Reproduced. Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: 014633f83e44ae8ba33087b6f38e8e253e281969 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-15_06:21:44 Locale: fi-FI (fi_FI)
*** Bug 98497 has been marked as a duplicate of this bug. ***
** 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
*** Bug 114161 has been marked as a duplicate of this bug. ***
Still repo in Version: 6.1.0.0.alpha1+ Build ID: 8010f473c77b9f384a7067f487bc24469f8c0cd3 Bartosz, You've made similar fixes in this area. Is this something you could take a look at?
Confirmed that there is missing Data Point field in attachment 121286 [details]: http://www.datypic.com/sc/ooxml/e-draw-chart_dPt-1.html After adding Data Point field: <c:dPt> <c:idx val="0"/> <c:invertIfNegative val="0"/> <c:bubble3D val="0"/> <c:spPr> <a:solidFill> <a:srgbClr val="FF0000"/> </a:solidFill> <a:ln> <a:noFill/> </a:ln> <a:effectLst/> </c:spPr> </c:dPt> into xl\charts\chart1.xml, it's working perfectly fine.
The code responsible for export Data Points is available at: https://github.com/LibreOffice/core/blob/master/oox/source/export/chartexport.cxx#L3247
Balazs Varga committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=c958f52b813d34baa9b5236bb34a08a04e6b0aba tdf#96469 Export Data Point properties in Charts on DOCX/XLSX It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Balazs Varga committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=15035b98dc694bde4c4073fa75bdd2ce9d7e6670&h=libreoffice-6-1 tdf#96469 Export Data Point properties in Charts on DOCX/XLSX It will be available in 6.1.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Balazs Varga committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6fa9aaaa5dca4d6b79698b55a2f2c956c99c3482&h=libreoffice-6-0 tdf#96469 Export Data Point properties in Charts on DOCX/XLSX It will be available in 6.0.7. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Balazs Varga, Thank you so much for fixing this bug. It's an issue I've observed in multiple docs in the wild. Is there a reason you have left this issue open as traditionally a the developer closes it when he feels it's done. Verified fixed in Version: 6.2.0.0.alpha0+ (x64) Build ID: dff829e863fd05bedd5bcb713cd80c10fa582932