Created attachment 46765 [details]
Downstream bug may be found at:
1_ lsb_release -rd
Description: Ubuntu 11.04
2) apt-cache policy libreoffice-calc
*** 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
3) What is expected to happen in LibreOffice Calc via the Terminal:
cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/681080/+attachment/1743794/+files/OO_DCOUNT_problem_2.ods && localc -nologo OO_DCOUNT_problem_2.ods
is Sheet 1, cell B19's formula:
throws an error as it is a malformed expression pointing to a non-existent column 0.
4) What happens instead is it erroneously yields 5. Occurs in both Ubuntu LO & 3.4.0 Beta.
this is not a bug
as http://wiki.services.openoffice.org/wiki/Documentation/How_Tos/Calc:_DCOUNT_function mentions 0 is used for all columns
(In reply to comment #1)
> this is not a bug
> mentions 0 is used for all columns
email@example.com, as mentioned in the above link:
The exact use of 0 as the field parameter is unclear, both in operation and in compatibility (issue 84168)".
As well, Microsoft clears up what it means via:
The field parameter is not supposed to have a 0 in it as field is the column to use. A 0 column does not make sense. Hence, LO should throw an error for Excel compatibility reasons (Gnumeric also throws the error appropriately).
No we are not Excel and we have our own formula api. As mentionen in the link I posted O is allowed and refers to all columns.
This is not a bug but a feature! We are not a excel copy so we don't need to behave in the same way.
firstname.lastname@example.org, thank you for your attention on this issue.
(In reply to comment #3)
> No we are not Excel and we have our own formula api.
I never said LibreOffice was Excel.
> As mentionen in the link I posted O is allowed and refers to all columns.
While 0 is currently allowed, it does not hold compatibility with Excel or Gnumeric as noted in Comment #2.
> This is not a bug but a feature!
Ok, this bug has been remarked as ENHANCEMENT.
As Markus already explained that this is a feature - it's not getting changed. Markus is one of our most experienced developers. Please don't reopen the bug.