For example, if you apply this formula: =IMPOWER("2+3i";1/2) Result is: 1.67414922803554+0.895977476129838i When for Croatian locale it should be: 1,67414922803554+0,895977476129838i Code pointer: ::GetString() in source/analysis/analysishelper.cxx
It's same with other formulas which work with complex numbers, for example IMPRODUCT. I tested this on croatian, HR, locale, but there is report that portuguese language have same problems.
** 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 (4.4.1 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-16
Yes, it's still present in 4.4.2.1 on Windows 8.1 64bit. It's also present in 3.3.2 so I guess it's bug from OO.
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
On Linux, if we start LibreOffice with for example: LC_NUMERIC=hr_HR.UTF-8 instdir/program/scalc Then =IMPOWER("2+3i";1/2) will be printed as 1,67414922803554+0,895977476129838i Because the decimal separator in format code of snprintf at http://opengrok.libreoffice.org/xref/core/scaddins/source/analysis/analysishelper.cxx#972 depends on the LC_NUMERIC part of the locale. At least this is the case under Linux. I'm not sure about Windows. Anyhow, LibreOffice has its own locale setting, ideally it should be used instead of LC_NUMERIC and snprintf.
(In reply to Andras Timar from comment #5) > At least this is the case under Linux. I'm not sure about Windows. > > Anyhow, LibreOffice has its own locale setting, ideally it should be used > instead of LC_NUMERIC and snprintf. On windows it's dot instead of comma. Tested with latest 5.1.2. Why enhancement when it's bug?
(In reply to Mikeyy - L10n HR from comment #6) > On windows it's dot instead of comma. Tested with latest 5.1.2. Thanks for testing. > Why enhancement when it's bug? OK, it's a minor bug then. In fact, it should depend on the cell's language.
** 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.2.7 or 5.3.3 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-20170522
Still valid. Version: 6.3.0.0.beta1 Build ID: a187af327633f5f00363be5131bd21a13e0f1a7b CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-AT (de_AT.UTF-8); UI-Language: en-US
Dear Andras Timar, 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
Still valid. Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: 4fbc246c7021248e4e9689f59b030b4b8f526954
This bug is still present 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 It is also present 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
*** Bug 156420 has been marked as a duplicate of this bug. ***
FWIW, are we all sure that we want a different decimal separator dependent on locale settings for complex numbers? Are other spreadsheet tools also have such distinction?
(In reply to ady from comment #14) > FWIW, are we all sure that we want a different decimal separator dependent > on locale settings for complex numbers? Are other spreadsheet tools also > have such distinction? I can only speak for Excel on Windows, with a French locale: indeed, the results of complex functions follow the regional settings. By default the decimal separator is a comma, and it's a comma in complex numbers in Excel as well. If the regional settings are changed to something else in Windows parameters, the change is reflected in Excel, including the results of complex functions.
I was unable to replicate this bug on windows version: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_DE); UI: en-US Calc: CL threaded
Don't have latest LO installed since it had big bugs, but 7.6.6.3 still shows formula from bug description with decimal point.
Created attachment 193578 [details] Problem in 24.8 persits
A proposed patch is here. Unfortunately, it does use the current cell formatting but the document locale: https://gerrit.libreoffice.org/c/core/+/162889 Assigned to new due to lack of time.