Created attachment 84366 [details] A LibreOffice Writer file where the error can be see. Problem description: The problem occurs in LibreOffice Writer, at “Conditional Text”. Large numbers, in Portuguese, are separated by points, not comas. When a number with two points, like 9.999.999 is used as result of a condition, no result is showed. Steps to reproduce: NOTE: the signs < and > are used only as delimiters. 1. Define a text variable as follow <XYZ>. 2. Initialize it with <S>. 2. Make three tests using “Conditional Text”, following these cases: CASE 1: if <XYZ EQ "S"> then <1 622.> else <123456> The result (OK) will be <1 622.> CASE 2: if <XYZ EQ "S"> then <1.622_> else <123456> The result (OK) will be <1.622_> CASE 3: if <XYZ EQ "S"> then: <1.622.> <-- Attention to two points. else <123456> The result (NOT OK) will be nothing. Current behavior: In CASE 3 nothing is showed. Expected behavior: The result should be <1.622.> Operating System: Windows 8 Version: 4.0.4.2 release
Thank you for your bug report, I CAN'T reproduce this bug running Version: 4.1.1.2 Build ID: 7e4286b58adc75a14f6d83f53a03b6c11fa2903 on Mac osx 10.8.4.
whoops some thing went wrong, I CAN reproduce this bug running Version: 4.1.1.2 Build ID: 7e4286b58adc75a14f6d83f53a03b6c11fa2903 on Mac osx 10.8.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 (4.4.1 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 *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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
Confirmed with attachment 84366 [details]. Did not try to repro, as instructions too sparse. Win 7 Pro 64-bit Version: 5.0.0.0.alpha0+ (x64) Build ID: 211c12b9c64facd1c12f637a5229bd6a6feb032a TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-18_01:51:17 Locale: fi_FI
Some more information: (1) The bug occurs if there is more than one dot in the conditional text. That means, that also conditional texts with letters are not displayed. E.g. "abc.def." is not displayed. (2) Also a conditional text with more than one dot in the 'Else' case is not displayed. (3) The bug does not occure if the first character of the conditional text is a dot. E.g. ".abc.def." is displayed. (3) 2 dots directly one after another are counted as one dot. That means "abc..def" is displayed but "abc..def." is not displayed. Win7 32 bit, Libo: 5.0.1.2.
** 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-20161108
Bug still exists in version 5.3.0. Bug already exists in version 3.3.0. Hence inherited from OOO.
** 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
Bug checked with version 6.0.1 (64 bit, Win 10). Bug still exists according original description.
Dear Roberto Guimarães, 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
Possibly bug 108112 is a DUP.
*** Bug 120758 has been marked as a duplicate of this bug. ***
*** Bug 108112 has been marked as a duplicate of this bug. ***
The problem lies in [1] where the fields are being evaluated. It will be assumed that everything containing two dots will be a database field. However, I couldn't insert a condition where its true/false value comes from a database, e.g.: test_case.Contacts.Title=="Engineer" from bug 120758 Neither one of the conditions evaluate to the content of the database field: test_case.Contacts.Title Contacts.Title Title Is this another bug or shouldn't we evaluate the true/false conditions to database fields in [2]? Yet another workaround is to escape the fields using double quotes "1.622.". [1] https://opengrok.libreoffice.org/xref/core/sw/source/core/fields/docufld.cxx?r=3020dfbe#1358 [2] https://opengrok.libreoffice.org/xref/core/sw/source/core/fields/docufld.cxx?r=3020dfbe#1392
Created attachment 191479 [details] A sample mail merge testcase (In reply to Andreas Heinisch from comment #14) > However, I couldn't insert a condition where its true/false value comes from > a database The attachment is a ZIP with two douments: - foobar_db.ods - a "database" with two fielda and three records; - foobar_mm.odt - a mail merge document, having a paragraph with a condition based on database field value. It works here, using Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded e.g., when printing the ODT, agreeing to pring a form letter, and saving the result to a single file, you see that page 2 has the paragraph with the condition correctly hidden, unlike pages 1 and 3.
Created attachment 191484 [details] Conditional Text Field Value Thank you Mike for the test case where it works in the merge case. In the attachment I tried to add a conditional text field using foobar_db.Sheet1.bar as the then value. This does not work? Or am I missing something?
Created attachment 191485 [details] Updated mail merge ODT Works here. This is a replacement for the ODT in the ZIP attached earlier.
Andreas Heinisch committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/74f25206bc5a1a36b85683555cb27179e5da3275 tdf#68364 - Don't assume a database if only two dots are present It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Andreas Heinisch committed a patch related to this issue. It has been pushed to "libreoffice-24-2": https://git.libreoffice.org/core/commit/57d32cde67239f6723dfb09d8809c989f4c3bf78 tdf#68364 - Don't assume a database if only two dots are present It will be available in 24.2.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Thanks, it works now for me 👍 Version: 24.2.0.1 (X86_64) / LibreOffice Community Build ID: b4d45829793cddfe67b58a53f495528c75738d8a CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded