Bug 106523 - CALC discrepancies and gaps
Summary: CALC discrepancies and gaps
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Localization (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Help-Changes-Features
  Show dependency treegraph
Reported: 2017-03-13 17:44 UTC by gmarco
Modified: 2019-04-03 21:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

CALC-inf_funct 1 (33.68 KB, image/jpeg)
2017-03-13 17:44 UTC, gmarco
CALC-inf_funct 2 (73.84 KB, image/jpeg)
2017-03-13 17:45 UTC, gmarco
CALC-inf_funct 3 (143.64 KB, image/jpeg)
2017-03-13 17:46 UTC, gmarco
CALC-inf_funct 4 (128.51 KB, image/jpeg)
2017-03-13 17:47 UTC, gmarco
CALC-inf_funct 5 (61.59 KB, image/jpeg)
2017-03-13 17:48 UTC, gmarco
CALC-inf_funct 6 (114.66 KB, image/jpeg)
2017-03-13 17:48 UTC, gmarco
CALC-spreads_funct 1 (176.68 KB, image/jpeg)
2017-03-13 17:49 UTC, gmarco
CALC-spreads_funct 2 (256.52 KB, image/jpeg)
2017-03-13 17:50 UTC, gmarco
CALC-spreads_funct 3 (98.56 KB, image/jpeg)
2017-03-13 17:50 UTC, gmarco
examples for CERCA (LOOKUP) (17.82 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-03-13 17:55 UTC, gmarco
screensh (168.43 KB, image/jpeg)
2018-03-15 11:52 UTC, gmarco
EN screensh (158.39 KB, image/jpeg)
2018-03-15 11:52 UTC, gmarco
details about help bugs (9.76 KB, application/vnd.oasis.opendocument.text)
2019-03-18 11:50 UTC, gmarco
test for CERCA-TROVA-RICERCA (20.22 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-03-18 11:51 UTC, gmarco

Note You need to log in before you can comment on or make changes to this bug.
Description gmarco 2017-03-13 17:44:39 UTC
Created attachment 131857 [details]
CALC-inf_funct 1

I think (and not just only me) the documentation (helps, guides, examples) has its importance.
So I point out some discrepancies and gaps in IT documentation as evidenced by the attachments (such as N instead of NUM, VALDISPARI and VAL.DISPARI_ADD instead of VAL.DISPARI, and some notes applying to the EN version but not for IT, etc.).
What shown applies to both the local and the online documentation.
I also feel that in many cases it is also proper to insert explanatory examples, at least when the interpretation of the text is not exactly simple: it is the case of the functions CERCA for which I had to resort to the help of corresponding products. In this regard, I attach a simple spreadsheet support.
Comment 1 gmarco 2017-03-13 17:45:54 UTC
Created attachment 131858 [details]
CALC-inf_funct 2
Comment 2 gmarco 2017-03-13 17:46:39 UTC
Created attachment 131859 [details]
CALC-inf_funct 3
Comment 3 gmarco 2017-03-13 17:47:23 UTC
Created attachment 131860 [details]
CALC-inf_funct 4
Comment 4 gmarco 2017-03-13 17:48:02 UTC
Created attachment 131861 [details]
CALC-inf_funct 5
Comment 5 gmarco 2017-03-13 17:48:45 UTC
Created attachment 131862 [details]
CALC-inf_funct 6
Comment 6 gmarco 2017-03-13 17:49:26 UTC
Created attachment 131863 [details]
CALC-spreads_funct 1
Comment 7 gmarco 2017-03-13 17:50:14 UTC
Created attachment 131864 [details]
CALC-spreads_funct 2
Comment 8 gmarco 2017-03-13 17:50:57 UTC
Created attachment 131865 [details]
CALC-spreads_funct 3
Comment 9 gmarco 2017-03-13 17:55:12 UTC
Created attachment 131866 [details]
examples for CERCA (LOOKUP)
Comment 10 Gabor Kelemen 2017-03-14 08:01:24 UTC
These are mostly localization problems, assigning to the Localization product.
The "still English sentence" problems are probably due to bug #94438 but I did not investigated it much.
Comment 11 QA Administrators 2018-03-15 03:38:17 UTC Comment hidden (obsolete)
Comment 12 gmarco 2018-03-15 11:51:21 UTC
(In reply to QA Administrators from comment #11)
> ** Please read this message in its entirety before responding **
Update (LO
Regarding the attachments "CALC-inf ..." NOTHING changed
Regarding the attachments "CALC-spreads ..." all text appears now in IT but the help informations are still inadequate and lacking in examples.
For example: about the formula "= SEARCH (0.8,A2:A4;C2:C4) getting #N/A" exemplified in the "examples for CERCA (LOOKUP)" attached on 2017-03-13 the result #N/A is not documented!
Another example (new attachments CERCA (IT).JPG and CERCA (EN).JPG): the proposition "If LOOKUP can not find the search criterion, it matches the largest value in the search vector that is less than or equal to the search criterion" is incorrect and, in the IT version, even incomprehensible because the subject is missing ("Se CERCA non può trovare il criterio di ricerca, corrisponde al valore più grande nel vettore di ricerca, il quale è inferiore o uguale al criterio di ricerca"); the correct diction should be "Se CERCA ...., il risultato corrisponde al valore inferiore più grande nel vettore di ricerca"
and in EN "... that is less than to the search criterion".

The reason is elementary:
who/what "corrisponde"?  certainly "il risultato"; 
why "inferiore o uguale" (EN "less than or equal to" if the assumption is that "can not find"?
Comment 13 gmarco 2018-03-15 11:52:11 UTC
Created attachment 140647 [details]
Comment 14 gmarco 2018-03-15 11:52:58 UTC
Created attachment 140648 [details]
EN screensh
Comment 15 QA Administrators 2019-03-16 03:56:28 UTC Comment hidden (obsolete)
Comment 16 gmarco 2019-03-18 11:49:04 UTC
(In reply to QA Administrators from comment #15)
> ** Please read this message in its entirety before responding **

Since March 2017, it is the second time you ask for a new test, but currently nothing has changed yet.
I'm using LO (IT), so, assuming the corrections have to be made by those who know IT, I expose the situation in IT, being a clear explanation in EN-US too complicated
See the attachments:
Bug 106523-details.odt
Bug 106523-test CERCA-TROVA-RICERCA.ods
Comment 17 gmarco 2019-03-18 11:50:28 UTC
Created attachment 150046 [details]
details about help bugs
Comment 18 gmarco 2019-03-18 11:51:38 UTC
Created attachment 150047 [details]
Comment 19 Valter Mura 2019-04-03 11:30:03 UTC
I'll be on it as soon as possible.

Where possible, corrections will be made. Gmarco, maybe I will need to contact you directly, by different means than the bug report.

Note that if there are errors / typos in the English version of the Help, they should be redirected to the Documentation Team, I can only work on the localized version.
Comment 20 gmarco 2019-04-03 16:04:46 UTC
Hi Valter, you know my mail address, write t me when you want (in IT, sure)!