Created attachment 168502 [details] source of xlsx with graph errors LO 7.04.2 x64 to Some basic functions in graphs are not converted to xlsx. So x and y axle legends disappear or change. See examples on the sheet like "AT" with graphs after saving of ods in xlsx. Saving of ods and xlsx is very slow in relation to xlsx in MSO 2016.
Created attachment 168503 [details] xlsx of source ods xlsx-file is signifikant smaller
Created attachment 168514 [details] Simple ODS example
I confirm the lost of legend in Version: 7.2.0.0.alpha0+ (x64) Build ID: ad9e04321df25824d2288a2ef1f4275f070f1cf7 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL Open Simple ODS example in LO, save it to XLSX and open XLSX in MS Excel => legens on chart are lost
Created attachment 168555 [details] The example file and its docx version in current master How it looks in: Version: 7.2.0.0.alpha0+ Build ID: 2577d9ecea199ca2c10d852cf279053a1b22faf7 CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded The X axis title should be exported, but this does not happen way back to: Verzió: 6.0.7.3 Build az.: 1:6.0.7-0ubuntu0.18.04.10 CPU szálak: 8; OS: Linux 5.0; Felületmegjelenítés: alapértelmezett; VCL: gtk3; Területi beállítások: hu-HU (hu_HU.UTF-8); Calc: group The secondary Y axis is different from Excel, there it is a different values axis and in Calc it's just a mirror of the primary axis.
Some users want also in single curve charts y-axles with numbers left and right. And that is also possible in MSO with XLSX. Loss of x-axle is here in action.
improved mostly but not perfect in LO 7.1.0.3 x64
Created attachment 172939 [details] other example (weather chart)
Created attachment 172940 [details] screenshot of the bad export of the chart only with secondary axis data seris Budapest is ok, but not Tokyo.
Created attachment 181047 [details] extended example paris tokyo budapest with budapest 2 Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: de-DE Calc: CL for me are Budapest and Budapest2 not ok. see attachment
Created attachment 181048 [details] extended example paris tokyo budapest with budapest 2 xlsx xlsx export with Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: de-DE Calc: CL for me are Budapest and Budapest2 not ok. see attachment
Dear paulystefan, 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