Created attachment 109849 [details] simple example OS: Kubuntu 14.04.1 x86 OpenSUSE 13.1 x86 Problem description: A currency format is wrongly extended when dividing sums of currency values. Steps to reproduce: 1. Open Calc 2. Fill in several cells with numbers. For extmple, 4 cells. 4. Select them, right-click and click format cells and give them currency format 3. Set cursor in the other cell and type =SUM(two cells)/SUM(other two cells) Current behavior: After putting mentioned formula in any cell, it chooses the currency format automatically. Expected behavior: When we divide some money by the other, we obtain the ratio. Therefore, the format should not be extended. For example, simply dividing one cell by another will not extend the format. I found this behavior in 4.2.7, maybe it was before.
I understand it and can reproduce it with LO 4.4.0.0.beta1 (Win 8.1), but I am not sure how this could be resolved, because for this maybe some kind of extensive elaboration or even artificial intelligence is necessary. LO needs then to check what is calculated with which cells and formats (e.g. a multiplication with another currency cell should stay as currency, summation should stay as currency etc.). But I don't know how this programmed, maybe there is also a simple solution and it is not that difficult. @Markus: Can you maybe help? Could this be resolved?
This mistake is not serious. Furthermore, the format can be removed through right-click -> Format cells. But it is not convenient. I told about the problem in hope that someone might want to fix it. If you want, I can describe the behavior in all possible mathematical operations. But I think, that we should not pay too much attention to this, little time is left to release 4.4. PS: If we can confirm a bug, do we need to give the status NEW now?
@Lera: Thank you very much for your fast reply. I agree with you that this no serious issue. And I can reproduce it, but in this case I would like to wait a little bit until Markus or any other CALC programmer/expert gives an additional feedback, whether we could mark it as a bug.
Created attachment 109908 [details] example in $US Setting NEW, adjusting summary. Division of two =SUM() functions holding currency formatted data is incorrectly assigned currency cell formatting. Which differs from the cell formatting assigned to a division of a =SUM() range by a single currency formatted cell. Another simple .ods example $US attached. Verified behavior back to 3.6 branch (don't have a 3.4 or 3.5 loaded at the moment) but as same behavior in current AOO builds we likely inherited this from OOo.
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
confirm on Version: 5.2.3.0.0+ ID: 4b7707bb8bcf0965d2d81f9c82672cb11829737f OS: Linux 4.6; local: ru-RU (ru_RU.UTF-8); Calc: group
** 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 tagezi, 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
https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr5.cxx?r=6f151be2#1632
Taking.
This does not happen anymore since LibreOffice 5.0 or so..