When using user-defined formats for cells in Calc, trailing semicolons are automatically removed. This is likely because Calc believes that the end result is incorrect; however, Excel treats the trailing semicolon as an exception rule for the format. To reproduce this problem in Calc, do the following steps: 1. Enter zero ('0') in the first two rows of the first column of a new spreadsheet (actual cell position is irrelevant). 2. Use "Format->Cells" menu or the "Format Cells..." right-click item to do custom formatting on the cell. 3. In the category list, select "User-defined." 4. Enter a Format code of "_($* #,##0.00_);_($* (#,##0.00);" Similarly, this can be reproduced in Excel: 1. Enter zero ('0') in the first two rows of the first column of a new spreadsheet (actual position is irrelevant). 2. Use "Format Cells" menu or the "Format Cells..." right-click item to do custom formatting on the cell. 3. In the category list, select "Custom." 4. Enter a Type of "_($* #,##0.00_);_($* (#,##0.00);" In both examples, only enter the formatting text between the quotation marks. Excel leaves the semicolon and formats the cell with a blank entry. Libreoffice Calc removes the semicolon and formats the cell using the existing entries with a result of "$0.00" The expected behavior is to simply blank out the cell if none of the entries match - the semicolon gives the exception case, similar to an else statement.
Reproduced the behavior in Version 4.0.0.0.beta2 (Build ID: 4104d660979c57e1160b5135634f732918460a0) on Ubuntu 12.04 (x86)
** 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.3.5 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) Thank you for your help! -- The LibreOffice QA Team
Still happens. Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+ Build ID: 07e84cae983c08afdba03018413a19d01abb3006 TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-19_06:15:38
** 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.5 or 5.1.0) 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: 2016-02-21
** 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.2.5 or 5.3.0 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-20170306
Taking.
Eike Rathke committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=8cb3faca4b1d1d9c68faba103c6c6117853e639e Resolves: tdf#52510 handle trailing ';' specifying empty following subformat It will be available in 6.0.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Pending review https://gerrit.libreoffice.org/41878 for 5-4
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-5-4": http://cgit.freedesktop.org/libreoffice/core/commit/?id=8a398429cd7b8369af360def49989623176cd233&h=libreoffice-5-4 Resolves: tdf#52510 handle trailing ';' specifying empty following subformat It will be available in 5.4.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
When utilizing client characterized designs for cells in Calc, following semicolons are consequently eliminated. This is likely on the grounds that Calc accepts that the outcome is off base; in any case, Excel regards the following semicolon as a special case rule for the organization. To repeat this issue in Calc, do the accompanying advances: 1. Enter zero ('0') in the initial two lines of the primary segment of another bookkeeping page (real cell position is insignificant). 2. Use "Configuration >Cells" menu or the "Arrangement Cells..." right-click thing to do custom organizing on the cell. 3. In the classification list, select "Client characterized." 4. Enter a Format code of "_($* #,##0.00_);_($* (#,##0.00);" Essentially, this can be recreated in Excel: 1. Enter zero ('0') in the initial two lines of the principal section of another bookkeeping page (genuine position is insignificant). 2. Use "Configuration Cells" menu or the "Organization Cells..." right-click thing to do custom arranging on the cell. 3. In the class list, select "Custom." 4. Enter a Type of "_($* #,##0.00_);_($* (#,##0.00);" In the two models, just enter the organizing text between the quotes. Dominate leaves the semicolon and configurations the cell with a clear section. Libreoffice Calc eliminates the semicolon and arrangements the cell utilizing the current passages with an aftereffect of "$0.00" The normal conduct is to just clear out the cell if none of the passages match - the semicolon gives the special case, like an else proclamation. From Source : https://faxcoversheetfree.com/
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/70dfe58b8b45a7221a1f6e335d0d4afcf0c1c026 tdf#52510: svl_qa_cppunit: Add unittest It will be available in 7.2.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.