Hi I have a cell containing 3 consecutive commas – ,,, I select the cell, then Data>Text to Columns>Separated by>Comma and the preview window shows 3 blank cells, as I would expect. However, when I click OK, the 3 consecutive commas remain in the original cell. Another example – I have a cell containing the text - ,2013-09-15 15:14:47,, I select the cell, then Data>Text to Columns>Separated by>Comma and the preview window shows [blank cell][2013-09-15 15:14:47][blank cell] as I would expect. When I click OK, and the original cell remain unchanged
Thank you for this feedback BugTriage : - search for duplicate (keywords = text to column) : Possible link with bug 51700 - information are clear - easy to reproduce (Windows 7, LibreOffice 4.0.5.2) Status changed to "new"
Graphic example of the problem can also be found in the related AskLO question: http://ask.libreoffice.org/en/question/23311/calc-how-to-split-correctly-cells-containing-commas/?answer=23314#post-id-23314
** 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
Created attachment 114605 [details] ODS example (created in v3.3.4.1). Re-tested under GNU/Linux x86_64 using: v3.3.4.1 OOO330m19 Build: 401 v3.4.6.2 OOO340m1 Build: 602 v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b v3.6.7.2 Build ID: e183d5b v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a v4.2.8.2 Build ID: 48d50dbfc06349262c9d50868e5c1f630a573ebd v4.3.5.2 Build ID: 3a87456aaa6a95c63eea1c1b3201acedf0751bd5 v4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 All versions exhibit the same behaviour: the preview is correct but the result mal-treats each row with a leading delimited (in this case comma).
As per comment 4, version set to "Inherited from OOo" and hardware set to All/All.
** 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
It is absolutely reproducible with LibreOffice 5.2.3.1 on Linux Debian amd64 and Windows 2008 Server, too. The "Text to Columns" shows blanks for blank fields, and/but does not overwrite those fields with blank, but leaves them as is.
Created attachment 128660 [details] Proposed patch
On master: diff --git a/sc/source/ui/docshell/impex.cxx b/sc/source/ui/docshell/impex.cxx index 9cfe424..c37875d 100644 --- a/sc/source/ui/docshell/impex.cxx +++ b/sc/source/ui/docshell/impex.cxx @@ -957,7 +957,7 @@ static bool lcl_PutString( { ScDocument* pDoc = &rDocImport.getDoc(); bool bMultiLine = false; - if ( nColFormat == SC_COL_SKIP || rStr.isEmpty() || !ValidCol(nCol) || !ValidRow(nRow) ) + if ( nColFormat == SC_COL_SKIP || !ValidCol(nCol) || !ValidRow(nRow) ) return bMultiLine; if ( nColFormat == SC_COL_TEXT ) getting rid of that rStr.isEmpty() optimization fixes this problem!
Tamás Gulácsi committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=96175a4bc6687c3adc31b9e0246fe49db2b7675e tdf#69981 - sc: blank empty cells in TextToColumns 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.
Zdeněk Crhonek committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=5f42c9527333034bd01d8b78fdc3c0eb9924d2cb uitest for bug tdf#69981 It will be available in 6.1.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.
The test exist, set status to Verified.