https://bugs.documentfoundation.org/show_bug.cgi?id=160985
--- Comment #16 from ady <adylo811...@gmail.com> --- (In reply to raal from comment #15) > See this > https://learn.microsoft.com/en-us/office/troubleshoot/excel/last-digits- > changed-to-zeros > Excel therefore stores only 15 significant digits in a number and changes > digits after the fifteenth place to zeros. Yes, I assumed that this is somewhat related to accuracy [1], as I mentioned in comment 7. But, if Calc can save the numeric value correctly (as shown by LO 3.3 when exporting to XLSX, and by the current export to XLS and by saving to ODS), shouldn't the value be saved accurately? I am in favor of Calc imitating the behavior of other spreadsheet tools regarding functions (e.g. SUMPRODUCT, VLOOKUP, etc.) and also imitating other aspects such as keyboard shortcuts. But, should accuracy limitations be a limit too? IOW, should Calc imitate this restriction seen in Excel? Or rather, perhaps let Excel apply its own accuracy limitations when opening the XLSX file (i.e. not-our-bug for such case), but maybe Calc should save the value accurately when it can. Are there negative consequences of such better accuracy? How Excel handles the value in the XLS equivalent file (which saves the correct value when exported by Calc)? I am unsure about this one, thus the questions. [1] <https://wiki.documentfoundation.org/Faq/Calc/Accuracy> -- You are receiving this mail because: You are the assignee for the bug.
