ODF 1.2 has deprecated the table:call-range-address as attribute of element <chart:plot-area>. Instead the attribute chart:values-cell-range-address of <chart:series> is used. http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#attribute-table_cell-range-address_element-chart_plot-area The use of this attribute with element <chart:plot-area> will be removed in ODF 1.4. Therefore it is time to change LibreOffice accordingly. I have made some tests with charts in Writer, Calc, Impress and Draw. I have generated a chart, then removed the attribute in file, and then reopened the file. In all my tests, the chart was the same as created. So it should be no problem to remove writing that attribute for ODF 1.4. I could not test charts in reports (REPORTBUILDER) because of crashes. The REPORTBUILDER seem to have severe problems with charts, see bug 117162, bug 117159, bug 87012 for example. I have looked at Pivot-Charts too. They have principle ODF related errors in cell addresses and need rework anyway, see bug 112785 and bug 112783. Old OOo versions use this attribute to distinguish between the cases, that the data source is the internal table of the chart, or the chart has an external data source. I have seen comments on this. So it might be, that import/export filter for these old versions still need to treat this attribute.
i can't find any recent changes to xmloff that would be relevant, it looks much like it did in 2008. reportdesign has this fun code: reportdesign/source/filter/xml/xmlExportDocumentHandler.cxx else if ( _sName == "chart:plot-area" ) { SvXMLAttributeList* pList = comphelper::getUnoTunnelImplementation<SvXMLAttributeList>(xAttribs); pList->RemoveAttribute("table:cell-range-address"); }
Dear Regina Henschel, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The task is still not solved in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 172e208e6b0674f42c301c5ee5e280e9138ba1b4 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
The task is still not solved in Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fbe57382eef1138999f63e01b6152d4d05749807 CPU threads: 32; OS: Windows 11 X86_64 (10.0 build 22631); UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded
The import of this attribute happens in https://opengrok.libreoffice.org/xref/core/xmloff/source/chart/SchXMLPlotAreaContext.cxx?r=12008e10#231 The export of this attribute happens in https://opengrok.libreoffice.org/xref/core/xmloff/source/chart/SchXMLExport.cxx?r=12008e10#1951 The latter file has some examples how to restrict saving to a special version. Look for SvtSaveOptions in the file. Searching for "xml_cell_range_address" in OpenGrog gives many unsuitable results, because the attribute is not only uses for element <chart:plot-area> but for a lot of other elements too, see https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#__RefHeading__1418294_253892949 Perhaps it is an easyHack. Because report builder and Pivot-Charts might be affected too, I think it is not a "Beginner" easyHack.
PivotCharts use the table:cell-range-address attribute for a purpose, that is unrelated to its meaning in older OOo version and that is not ODF conform at all, see bug 112783.
Simply not writing the attribute does not work. Then the unit test fails: chart2/qa/extras/uichart.cxx(70) : error : Assertion Test name: testTdf136011::TestBody equality assertion failed - Expected: A - Actual : B - Incorrect description in column: 0 The reason is not obvious. It seem so be somewhere in ScChart2DataProvider::detectArguments in chart2uno.cxx.
Regina Henschel committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/7cec59402d09077749cc6bbe96cbf19652d2d3d9 tdf#131862 No table:cell-range-address in ODF 1.4 It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
To verify: A) Open a chart produced in older version and save it in ODF 1.4. B) Save a document with chart in ODF 1.4 and reopen it. The chart should not have changed. C) Copy a chart from Calc to Impress or Draw. The visual appearance should be the same, only that the copy has the data in an internal table. D) Do A)-C) not only with simple charts but with multi-level categories and changed order of data series. In all cases, there must not exist table:cell-range-address as attribute of the <chart:plot-area> element in file format, when saved in ODF 1.4. The attribute may exist in other elements. The reason for the unit test failure mentioned in comment 8 is, that copying to clipboard had created an erroneous order of series, if only the attribute table:cell-range-address is no longer written. The solution in the patch is to not only omit table:cell-range-address attribute but also the related and already deprecated attributes chart:data-source-has-labels, chart:column-mapping and chart:row-mapping.