Created attachment 109660 [details] Example of irregulatities with labeled ranges The automatic detection of ranges when a label is used works counter-intuitive. cell references refer to the attachment. -a label for numeric data works for vertical ranges [A2, A21 and A22], but not for horizontal ranges [A3], unless the data is also in vertical ranges [A23 and A24]; -a label for textual data works for horizontal ranges [A5] but not for vertical ranges [A4]. -When both horizontal and vertical ranges are possible, the choice of the ranges seems to depend on the range being numeric [a6] or textual [A5].
@Erack: Eike, you worked on this code to fix fdo#59583. Do you know how the behaviour should be?
Automatic detection of labels is a mess anyway and counter-intuitive by definition ;-) I wish we never followed MS-Excel onto the dark path there, which in the mean time has that feature deprecated by the way.. How I understood the lookup we implemented is described in ODF http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.html#__RefHeading__1017956_715980110 I think the magic sentence here for this case is "If the resulting cell is below or above another cell containing Text a row lable is assumed, else a column label is assumed." Does that fit your observation?
Hi I reproduce & set status to New. I add two cases of "mixed" data (text & number) in the attached file Best Regards Pierre-Yves
Created attachment 109671 [details] label_range_irregularitiesV2
(In reply to Eike Rathke from comment #2) > I think the magic sentence here for this case is "If the resulting cell is > below or above another cell containing Text a row lable is assumed, else a > column label is assumed." Does that fit your observation? Yes, it does. For both attachments, actually. So, the gist is that the above magic sentence should be added to the help text of LibreOffice (preferably less cryptic). I changed the subject and the component of this report. Eike, thank you for your lightning-fast reply and link :-)
** 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 (5.0.4 or later) https://www.libreoffice.org/download/ 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 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Bug report is still valid (LO 5.0.4).
** 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 (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Lack of information in Help still occurring with LO version 5.2.4.2 (Windows7).
Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/9e32990654d9b4ad397f6e0d21973483b1bf47f9 tdf#86427 automatic label detection explanation