Created attachment 134284 [details] powers of 2 (2^0 .. 2^64) with fractional digits 0 .. 20, err in R49 .. V55 wrong display of powers of 2 from 2^47 until 2^53 when fractional digits are between 16 and 20 example: type in A1: =2^47, you get correctly: 140737488355328 press repeatedly the '0.00+' button to increase fractional digits, you get: 15 digits: 140737488355328.000000000000000 RIGHT 16 digits: 14073748835532.8000000000000000 WRONG 17 digits: 1407374883553.28000000000000000 WRONG 18 digits: 140737488355.328000000000000000 WRONG 19 digits: 14073748835.5328000000000000000 WRONG 20 digits: 1407374883.55328000000000000000 WRONG the wrong values are not only displayed on screen but also written out when you save in .csv format
On Win7 with LO 5.3.4 + brand new LO profile, I could reproduce this. clicking on button '0.00+' when display value is: 1407374883,55328000000000000000 does nothing. BTW, sum value at the bottom of window shows the same pb.
I reproduce with LO 5.1.0.3 Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737 CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; Locale : fr-FR (fr_FR) but not with LO 5.1.0.2 Build ID: ecd3574d51754b043f865cf5bafee286d24db7cc CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; Locale : fr-FR (fr_FR)
Maybe because it's trying to go beyond precision limits. Fifteen digits plus sign. The issue with csv it that it uses the formatted value not the underlying value, by default, but there is an option saving as csv to not use the formatted value.
** 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
Dear Carlo Verre, 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! Warm Regards, QA Team MassPing-UntouchedBug
looks ok with ver. 7.2.0.0.a0+, as well in a fresh sheet as when loading the OP sheet, will set WFM if no objections within next month, Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 6e6e531b564cdc9d5b25287c215cdc5a1fcbb346 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL
I don't reproduce this with LO Debian package 7.0.4.2 Let's put this one to WFM then. Of course, if someone can still reproduce this with a recent LO version (7.0.5 or 7.1.2) don't hesitate to reopen this tracker.