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.
Created attachment 131858 [details] CALC-inf_funct 2
Created attachment 131859 [details] CALC-inf_funct 3
Created attachment 131860 [details] CALC-inf_funct 4
Created attachment 131861 [details] CALC-inf_funct 5
Created attachment 131862 [details] CALC-inf_funct 6
Created attachment 131863 [details] CALC-spreads_funct 1
Created attachment 131864 [details] CALC-spreads_funct 2
Created attachment 131865 [details] CALC-spreads_funct 3
Created attachment 131866 [details] examples for CERCA (LOOKUP)
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.
** 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 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to QA Administrators from comment #11) > ** Please read this message in its entirety before responding ** > Update (LO 5.4.5.1) 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"?
Created attachment 140647 [details] screensh
Created attachment 140648 [details] EN screensh
(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 6.2.0.3 (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
Created attachment 150046 [details] details about help bugs
Created attachment 150047 [details] test for CERCA-TROVA-RICERCA
Hi, 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.
Hi Valter, you know my mail address, write t me when you want (in IT, sure)!
Dear gmarco, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Since March 2017, it is the third time you ask for a new test, but currently nothing has changed yet. I'm using LO 7.1.1.2 (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 new attachments: Bug 106523-details (upd 03.04.21).odt Bug 106523-test CERCA-TROVA-RICERCA (upd 03.04.21).ods @Valter Mura: look at comments #19-20
Created attachment 170936 [details] summary updated substantially like the previous
Created attachment 170937 [details] sample updated substantially like the previous
Dear gmarco, 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
Hi working on it. The highlighted string in the Help has been changed, waiting for approval by the Translation Team.
(In reply to QA Administrators from comment #25) > Dear gmarco, > > 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. > .... Hi, seeing the last comment by V.Mura let me wait for the news.