A version of this bug-report with screen-shots is here: <http://homefarmparham.co.uk/tmp/calc/IntersectCalcImportBug.html> In Calc, if you had selected Calc A1 Formula Syntax (the default), then you import a formula from MS Excel, an intersection operator that was <SPACE> in Excel A1 formula syntax correctly converts to the '!' operator. For example, if the formula in MS Excel on Windows was originally: =A2:C2 B1:B3+3 then after import, the Calc A1 formula syntax will (correctly) be: =A2:C2!B1:B3+3 For instance, if the number 7 is in cell B2, the output of the above formula will be 10. In Calc, if instead you had selected Excel A1 Formula Syntax (using Tools>Options>Calc>Formula), then you import a sheet from MS Excel, an intersection operator that was <SPACE> in Excel should appear unchanged as a <SPACE>. However, it incorrectly displays as the '!' operator as if it has converted to Calc Formula Syntax. For example, if the formula in MS Excel on Windows was originally: =A2:C2 B1:B3+3 then after import, the Excel A1 formula syntax will (incorrectly) show as: =A2:C2!B1:B3+3 When Calc is set to Excel A1 Formula Syntax, a '!' in this position should lead to an error, but instead it shows the result 10, which is therefore a bug. If you cut the formula and re-paste it into the same cell, it gives a #NAME? error, which is what you would expect. But it didn't give a #NAME? error before. This appears to only be a problem of how the underlying formula is displayed, not how it calculates (which is why I've categorised the severity as minor). I suspect what is happening here is that the Excel file format is converted to Calc A1 formula syntax as an internal representation, but then Calc is failing to display the underlying Calc syntax in the selected syntax (Excel A1). Everything said above about Calc's Excel A1 Formula Syntax applies equally to Calc's Excel R1C1 Formula Syntax. Everything said above about the intersection operator applies equally to the union operator (',' in Excel and '~' in Calc). For instance, after import, the Excel formula =SUM((A1:A3,B1:B3) A2:D2) displays in Calc as: =SUM((A1:A3~B1:B3)!A2:D2) irrespective of the selected formula synax. However, I can't think of a use for the union operator. Whereas, all my business's cash books use the intersection operator extensively. This may be related to bug 96426, but I've reported the two separately.
Please attach an example file coming from Excel. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the file.
Created attachment 121485 [details] example of bug 96429: intersection operator on 'intersection' sheet, and union and intersection operators on 'union_and_intersection' sheet To experience the bug, before opening the attachment, configure Calc using Tools>Options>Formula>Excel A1 Syntax. The attached file was saved from MS Excel 2002 (10.2614.2625) on Win XP SP2.
Confirmed. Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: 014633f83e44ae8ba33087b6f38e8e253e281969 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-15_06:21:44 Locale: fi-FI (fi_FI)
** 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.6 or 5.2.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-20170103
WFM now (as person who originally reported the bug) LibreOffice Version: 5.2.3.2 Build ID: 1:5.2.3~rc2-0ubuntu1~trusty1 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; Locale: en-GB (en_GB.UTF-8); Calc: group