Function in xlsx with logic answer gives 0 or 1 in LO while in MSO it gives TRUE or FALSE this can lead to differences when using conditional formatting.
Steps to Reproduce:
1. Create a new xlsx in Excel.
2. Create a function which gives back TRUE or FALSE.
3. Save it and open it in LO.
4. Notice the difference.
The function gives back 1 or 0.
It should give back TRUE OR FALSE just as it does in MSO.
User Profile Reset: No
Created attachment 147531 [details]
The original document.
Created attachment 147532 [details]
Screenshot of the original document side by side in Excel and Calc.
Build ID: 3c964980da07892a02d5ac721d80558c459532d0
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45
Locale: ru-RU (ru_RU); UI-Language: en-US
from scratch for ODS Calc shows in cells True or False
Also reproduced in
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.15; Render: default;
but not in
Version 18.104.22.168.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
I still haven't checked if the following lines are the culprit, but I suspect so.
<row r="1" spans="1:2" x14ac:dyDescent="0.25">
<c r="A1" t="b">
<row r="2" spans="1:2" x14ac:dyDescent="0.25">
<c r="A2" t="b">
<c r="B2" t="s">
This seems to have begun at the below commit.
Adding Cc: to Kohei Yoshida ; Could you possibly take a look at this one?
b24c5c64280698417f54375715aa07370f0d47d0 is the first bad commit
Author: Matthew Francis <firstname.lastname@example.org>
Date: Sat Sep 5 22:39:37 2015 +0800
Author: Kohei Yoshida <email@example.com>
AuthorDate: Thu Oct 31 17:53:02 2013 -0400
Commit: Kohei Yoshida <firstname.lastname@example.org>
CommitDate: Mon Nov 4 13:59:17 2013 -0500
Insert matrix formula vis ScDocumentImport, and more formula imorts.
Now SetGroupFormulaCell() is no longer used.
Dear NISZ LibreOffice Team,
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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Still a problem in:
Version: 22.214.171.124.alpha0+ (x64)
Build ID: e97a81e94511b52987a50b7bdb72c922899da588
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: en-US