Created attachment 132111 [details] XLS sample The attached XLS contains conditionally formatted cells with the predefined color schemes in Excel 2013. (Light Red Fill with Dark Red Text etc.) A lot of those colors are imported incorrectly, especially Dark Red, which is imported as purple. The rest are only slightly different. The same colors look okay when imported from XLSX. Color codes from Excel (text and background): A2: 156 / 0 / 6 255 / 199 / 206 B2: 156 / 101 / 0 255 / 235 / 156 C2: 0 / 97 / 0 198 / 239 / 206 D2: Automatic 255 / 199 / 206 E2: 156 / 0 / 6 No fill F2: Automatic No fill border 156 / 0 / 6 Color codes/names from Calc (text and background): A2: #800080 Pink 10 B2: #993300 Yellow C2: Green 5 Green 10 D2: Black Pink 10 E2: #800080 No fill F2: Black No fill border #800080 Reproduced with v5.3.1.2 & v3.3.0 / Windows 7.
Created attachment 132112 [details] XLSX sample
Created attachment 132113 [details] Comparison of colors between Excel and Calc (XLS)
Confirmed in Version: 5.4.0.0.alpha0+ Build ID: 1670cc25bc2771e87f7956a4b0dd634abaa4128b CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Seems to be related to missing CFEx and similar elements and structs in the xls import and export filter. I'm not sure if we want to implement these records. It looks like a huge mess and my documentation effort in oletoy shows that you most likely need some reverse engineering to implement them.
I have a similar, maybe more serious problem. In my job I must add data to a corporate XLSX file with color related conditional formatting. Every time I saved that file as XLSX in any version of Libre Calc prior to 5.4, all of the colors and conditional formatting were lost. My work around was/is awful. I have to download the file on my Linux system, yank out the cat5 cable, reboot into an unpatched copy of Windows, use an unpatched copy of MS Office to enter the data, reboot into Linux, re-insert the cat5 cable, upload the file, and repeat this process at least monthly. In my daily work all other XLSX files have no issues, but then they have no colors related conditional formatting. Recently I upgraded to Libre Office 5.4. Then I accidentally edited and saved that one special corporate XLSX file. I was shocked to find that the colors related conditional formatting seems to be intact! Could someone please confirm that there was a fix made to saving colors related conditional formatting in XLSX files between 5.3 and 5.4? If confirmed this may be my big chance to get rid of the old MS software.
Your issue is certainly unrelated to this one. Why don't you conduct further tests? No one will be able to tell you what kind of special bug your spreadsheet had, and how saving got fixed without looking at it. You could try creating a minimal sample for your tests, and work with that.
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still repro in 6.2 master build (8af4ea707e7ed63e65d75fd63cca02e018e4e16a) / Windows 7.
Dear Aron Budea, 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still the same in LO 6.4.0.0.alpha0+ (a40fbd031de042b0181dc5570164ae8ce0abb0f1) / Ubuntu 19.04.
*** Bug 137362 has been marked as a duplicate of this bug. ***
This bug is still able to reproduce in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: hr-HR (en_US); UI: en-US Calc: threaded Also is able to reproduce in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 105f057f5b994b7d79a55ca719240839c2d45b54 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: hr-HR (en_US); UI: en-US Calc: CL threaded