Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 206319 - app-office/openoffice{,-bin} - OOo Calc makes arithmetical errors
Summary: app-office/openoffice{,-bin} - OOo Calc makes arithmetical errors
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Office Team
URL: http://www.openoffice.org/issues/show...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-17 12:09 UTC by Heiko Baums
Modified: 2008-01-17 17:12 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Baums 2008-01-17 12:09:28 UTC
I imported a csv file into OOo 2.3.1 Calc and summed up a few cells with the function SUM(cellA:cellB;cellC:cellD). The result differs from the correct result around .01.

For some reasons I can't attach the table but I had these values in one of the tables:
cell L2: 3.9
cell L3: 0.57
cell L4: 1.25
cell L5: 0.76

In cell A7 I had this formular (in the German version):
=SUMME(L2:L5)

The correct result is: 6.48
OOo's result is: 6.47

With the formular
=L2+L3+L4+L5
I'm getting the same wrong result 6.47.

It doesn't matter in which cell the values are and how many values are summed up. This happened with several files and tables.

I already filed a bug report to upstream:
http://www.openoffice.org/issues/show_bug.cgi?id=85325
Comment 1 Andreas Proschofsky (RETIRED) gentoo-dev 2008-01-17 12:49:37 UTC
If this happens also with openoffice-bin, nothing we can do here, upstream is the right place. Thanks for pointing this out anyway
Comment 2 Heiko Baums 2008-01-17 13:05:32 UTC
I don't know if this also happens with openoffice-bin. Jakub added the "app-office/openoffice{,-bin} - " to the summary. So I'm reopening this bug just in case. 

I have only app-office/openoffice-2.3.1 installed. So I can't test it with openoffice-bin. Sorry for not mentioning the correct package version. I just copied and pasted my upstream bug. ;-)

But I guess that this is in fact an upstream bug. Maybe someone can test it with openoffice-bin.

My main intention was indeed just to inform you about this bug.
Comment 3 Dustin Polke 2008-01-17 14:57:48 UTC
Are you sure that you do not have set number format to 2 decimal places and filled in numbers with 3 or more? If this is the case, Oocalc internally still calculates with all decimal places and round AFTER the summation to the selected number of decimal places, which of course can differ from the sum of numbers rounded previously.

Dustin
Comment 4 Heiko Baums 2008-01-17 15:12:13 UTC
(In reply to comment #3)
> Are you sure that you do not have set number format to 2 decimal places and
> filled in numbers with 3 or more?

I'm sure that the number format of the cells was/is "Standard", so without a limitation of the decimal places because I've imported a csv (text) file and because I already checked this.

And for the same reasons I'm also sure that the numbers were entered exactly as I've written it in this bug report with 1 or 2 decimal places.

So it's not such a rounding error. Of course I calculated it manually. So I think that I would have noticed this if this was the case.

And, btw., for testing purposes I reformatted the cells to a currency format with 2 decimal places and the result was the same.

So it's definitely a bug in OOo Calc.
Comment 5 Heiko Baums 2008-01-17 17:12:12 UTC
Because of a comment in OOo's bugzilla I wanted to edit one of the csv files in a text editor and found out that I apparently haven't looked carefully enough at the values.

In the text editor the values had indeed 4 decimal places. So it was the problem Dustin Surawicz mentioned in comment #3.

But then I think there is another bug because OOo cuts the numbers to two decimal places when opening a csv (text) file even if the cell format is "Standard".

And this shouldn't have anything to do with the precision settings in the options.

Ok, I guess now I think what the decimal places in the options mean. This is a different problem. I think I'll file another bug report/feature request to upstream.

I guess I can close this bug as INVALID.