Bug 134765 - ROUND will not work with nested subcalls
Summary: ROUND will not work with nested subcalls
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Tables-Formulas
  Show dependency treegraph
 
Reported: 2020-07-13 00:09 UTC by Michael Warner
Modified: 2023-02-10 03:25 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example MS Word Document (13.33 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-07-13 00:09 UTC, Michael Warner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Warner 2020-07-13 00:09:25 UTC
Created attachment 162945 [details]
Example MS Word Document

When importing an MS Word document that contains a table with a formula that contains a ROUND call with nested subcalls to other functions, the formula is not imported correctly. For example, ROUND(MIN(A1,B1), MAX(C1,D1)) will not be translated correctly.
Comment 1 Mike Kaganski 2020-07-13 03:20:57 UTC
... but it will not import just any formula with function - be it ROUND or SUM; be it simple or nested. So why that level of precision?

Writer has a very different formula syntax: it should be like "2.3456 round 3", not "round(2.3456, 3)". As far as I know, we don't try to convert the function syntax from/to Word syntax to Writer syntax both on load ans save.
Comment 2 Michael Warner 2020-07-13 14:19:05 UTC
I should add that this will still be the case after my proposed patch which converts simpler calls to ROUND() and other functions to Writer syntax. 

https://gerrit.libreoffice.org/c/core/+/98614

What I am pointing out in this bug is that patch will make the formula import situation better, but not completely resolve it.
Comment 3 QA Administrators 2023-02-10 03:25:39 UTC
Dear Michael Warner,

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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug