Created attachment 76139 [details] correct and incorrect cell formatting examples Problem description: -------------------- The cell-formatting parser does not recognize the semicolon inside quotation marks (as string limiter) correctly as string, as the semicolon is also used as separator between positive and negative format information. Steps to reproduce: ------------------- a1. Select some cells a2. Open 'Format cells...' dialogue a3. Select 'user-defined' a4. Enter first format code "L#"0"s@";"L#"-0"s@" (with quotation marks) a5. Click OK a6. Enter a number (e.g. '123') into one of the formatted cells a7. Displayed result is 'L#123s@' (= correct) a8. Enter a negative number (e.g. '-123') into one of the formatted cells a9. Displayed result is 'L#-123s@' (= correct) b1. Select some cells b2. Open 'Format cells...' dialogue b3. Select 'user-defined' b4. Enter second format code "L#"0"s;";"L#"-0"s;" ('@' is replaced by ';') b5. Click OK b6. Enter a number (e.g. '123') into one of the formatted cells b7. Displayed result is 'L#123"s' (= incorrect) b8. Enter a negative number (e.g. '-123') into one of the formatted cells b9. Displayed result is '"' (= incorrect) Expected behaviour: ------------------- User-defined cell formatting of number (e.g. '123') shall lead to output like 'L#123s;' (with 'L#" before the number and 's;' after the number).
Comment on attachment 76139 [details] correct and incorrect cell formatting examples changed Mime-Type to image/png
I can confirm this behaviour also in Version 3.6.4.3 , German version on Windows7x64 Professional SP1 Intel Core i5 CPU, M480@2.67GHz 2.66 GHz RAM 8 GB (7.8 GB eff.)
** 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.0.3 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 This NEW Message was generated on: 2015-02-19
I can confirm this behaviour also in Version 4.3.6.2, German Mac version.
I can confirm this behaviour also in version 4.4.1.2, English Mac version, on Macbook with OSX 10.9.5 (Mavericks).
** 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.2 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-04-16
The bug is still present. LibreOffice Version 5.0.5.2 Operating system: OS X El Capitan 10.11.4
Workaround: do not insert semicolon inside quotes, but with an escape character. For instance: "L#"0"s"\;;"L#"-0"s"\;
Thanks for your response. To be honest - I'm not waiting 3 years to get a suggestion for a workaround. I already found one by myself in March 2013, a I needed the function. I know that there is a lot of work to do around LibreOffice. But there is no motivation for me to report bugs if they are not fixed within acceptable time. The bug in parser needs to be fixed. Workarounds don't make LibO better.
Laurent Balland-Poirier committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=88a79589843efc24f8af99bd511a1fff0f7bebef tdf#61996 Skip quoted text in number format It will be available in 5.2.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.
Eike Rathke committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=7a8331eb7f4e782cd9febc9923b99d4c02cd2945 fix export crash test due to assert hit, tdf#61996 follow-up It will be available in 5.2.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.
Laurent Balland-Poirier committed a patch related to this issue. It has been pushed to "libreoffice-5-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=9a2b656dbd4acadcfc144ba8db7c9657c7a72f1f&h=libreoffice-5-1 tdf#61996 Skip quoted text in number format It will be available in 5.1.4. 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.
Laurent Balland-Poirier committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=93874236610dd50a46b6db229e022ae364af582a tdf#97835 tdf#61996 tdf#95339 Add qa unit test It will be available in 5.3.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.