Bug 59550 - Incorrect tooltips for new ...IFS functions
Summary: Incorrect tooltips for new ...IFS functions
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) rc
Hardware: Other All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2013-01-18 09:21 UTC by GerardF
Modified: 2015-03-28 21:36 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:

SUMIFS with locale settings in french (8.93 KB, image/jpeg)
2013-01-18 09:37 UTC, GerardF

Note You need to log in before you can comment on or make changes to this bug.
Description GerardF 2013-01-18 09:21:51 UTC

Comment 1 GerardF 2013-01-18 09:37:55 UTC
Created attachment 73240 [details]
SUMIFS with locale settings in french

With locale using semicolon separator for functions (comma as decimal separator) like French, tips are incorrect.

When writting or editing a formula SUMIFS, tips display :
SUMIFS( sum_range; range 1, criteria 1; range2, criteria 2; ... )

Note that separator between range_x and criteria_x is a comma. Should be a semicolon.
It is confusing for the user editing the formula because when you put the cusor in criteria_1 the arrow ► is in range_2.

See screenshot.

Work fine in locale using comma as function separator like English.
Comment 2 pierre-yves samyn 2013-06-16 04:36:30 UTC

I Confirm with windows 7 64bits &

The tooltip does not reflect the local setting between  "range" and "criteria" (always uses a comma).

This impacts the wizard function and the function list too.

This defect leads users error...

Comment 3 QA Administrators 2015-03-16 22:48:51 UTC
** 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 (4.4.1 or later)

    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)


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 your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-03-16
Comment 4 Jean-Baptiste Faure 2015-03-28 21:36:38 UTC
Tips use only semicolon in French. So closing as WorksForMe.

Please, feel free to reopen if you disagree.

Best regards. JBF