Description: Saving a calc document in native LibreOffice format with a formula using a blank between function name and initial parentheses may lead to a file which may not be successfully opened by Excel. This is very similar to the problem 104186 I reported earlier (and which was fixed afterwards). LO seems to violate paragraph 5.14 (titled "Whitespace") of the document "OASIS Open Document Format for Office Applications (OpenDocument) Version 1.2" which clearly states: "whitespace shall not separate a function name from its initial opening parentheses." If I manually remove the invalid blank from the LO save, Excel can open the saved LO file successfully. Steps to Reproduce: 1. Create a blank document with LO calc sheet with LO 6.2.2.2, using German localisation 2. Use in the document the parameterized function JAHR (German for YEAR), and use a cell reference as parameter for JAHR. In the formula, add a space character between the function name and the initial brace. 3. Save the document in default LO format (.ods) 4. Open the document with a German version of Microsoft Excel 2016. 5. Excel reports an error for the cell with the JAHR function 6. Repeat steps 1 to 5, but do not add an additional blank. Result: Excel opens the file successfully. Actual Results: Error message in Excel when opening the LO file Expected Results: No error message by Excel when opening the LO file Reproducible: Always User Profile Reset: No Additional Info: The application must not save any whitespace between a function name and the initial opening parentheses. In my understanding this violates ISO/IEC 26300-1:2015. See also bug 103186 where the same issue was resolved for saves in ECMA-376 (Excel) format, which has the same constraints concerning illegal space characters between function name and initial brace.
Created attachment 150614 [details] Testcase for bug 124164 (does cause an error when opened with Excel) Test case for bug 124164 which causes an error when opened with Excel
> Saving a calc document in native LibreOffice format with a formula using > a blank between function name and initial parentheses may lead to a file > which may not be successfully opened by Excel. reproducible, cell A1 shows #NAME? (excel 2016) btw: saving attached *.ods as *.xls/*.xlsx works fine with excel
(In reply to Oliver Brinzing from comment #2) > btw: saving attached *.ods as *.xls/*.xlsx works fine with excel Yes, this is because of the earlier fix for bug 104186!
Sorry, there was a typo in my earlier contributions: the related closed bug is 104186 (not 103186)
Dear Victor V. Terber, 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
Re-tested with LO 7.2.0.4 (x64): Bug no longer reproducible.