Description: Search and Replace does not find empty paragraphs in textfile with CRLF line endings. Works okay when creating new file and when opening file with only CR endings. Steps to Reproduce: 1. Create new txt file on Linux like: line one <empy line, just hit Enter> <empy line, just hit Enter> line two Likely it is going to have CR-only line endings. 2. Load it into Writer (File/Open or New Document->Insert->Document 3. Open Search and Replace (Ctrl-H), check regular expressions and search for ^$ (empty paragraph) 4. It works. 5. Close file, change it to have CR/LF line endings, for exaple with the unix2dos command line tool. 6. Repeat steps 2-3. 7. Search phrase not found. Tried with 5.2.3.2 Build: 1:5.2.3~rc2-0ubuntu1~xenial1 installed from deb http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial main No idea if other regexps work. Actual Results: Search and Replace does not find empty paragraphs. Expected Results: Search and Replace should find empty paragraphs. Reproducible: Always User Profile Reset: No, it was a fresh test install of Xubuntu 16.04 Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/55.0.2883.87 Chrome/55.0.2883.87 Safari/537.36
Created attachment 130171 [details] Text file with empty paragraphs and DOS line endings I converted it with Kate editor Tools - End of line. LibreOffice 3.3 actually asks me about the line endings on import and the finding works, if I say CR & LF! I wonder, why this feature was removed. It is already gone in 3.6. Bug 31480 is somewhat relevant. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 1a58cdf8af1aba52ce0a376666dd7d742234d7cf CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on January 4th 2016 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b) Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
(In reply to Buovjaga from comment #1) I think the main concern is not the removal of line endings dialog but the fact that the regexp search apparently depends on something it is not supposed to.
** 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
As asked for in Comment 3, re-checked, repeating stetps in original report. Bug present in: Latest release running on Ubuntu 17.04: Version: 5.4.4.2 Build ID: 2524958677847fb3bb44820e40380acbe820f960 CPU threads: 1; OS: Linux 4.10; UI render: default; VCL: gtk2; Locale: en-US (C); Calc: group Version: 5.4.4.2 Build ID: 2524958677847fb3bb44820e40380acbe820f960 CPU threads: 1; OS: Linux 4.10; UI render: default; VCL: gtk2; Locale: hu-HU (hu_HU.UTF-8); Calc: group Release coming with Ubuntu 17.04: Verzió: 5.3.1.2 Build az.: 1:5.3.1-0ubuntu2 CPU szálak: 1; Rendszer verziója: Linux 4.10; Felületmegjelenítés: alapértelmezett; VCL: gtk3; Elrendezésmotor:új; Területi beállítások: hu-HU (hu_HU.UTF-8); Calc: group Release coming with Ubuntu 16.04: Verzió: 5.1.6.2 Build az.: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU szálak: 4; Rendszer verziója: Linux 4.4; Felületmegjelenítés: alapértelmezett; Területi beállítások: hu-HU (hu_HU.UTF-8); Calc: group
Dear Varga Péter, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Version: 7.2.4.1 (x64) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 1; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
This was not a bug at all. Putting it here just for completeness, to help archaeology. (In reply to Buovjaga from comment #1) > LibreOffice 3.3 actually asks me about the line endings on import and the > finding works, if I say CR & LF! I wonder, why this feature was removed. It > is already gone in 3.6. The default filter for TXT files is now "Text", unlike the previous default choice of "Text - Choose Encoding" (previously "Text Encoded"). The latter can be chosen manually when opening from LibreOffice's File Open dialog, to allow customizing. Compare to the long-standing request tdf#74580 to skip the dialog when opening CSV. (In reply to Varga Péter from comment #0) > ... search for ^$ (empty paragraph) > 4. It works. > 5. Close file, change it to have CR/LF line endings, for exaple with the > unix2dos command line tool. > 6. Repeat steps 2-3. > 7. Search phrase not found. This should *not* work. When you open such a file without explicitly saying that CRLF is the paragraph boundary, the file is opened using system line ending convention for paragraph boundaries. Thus, on Linux only LF will be detected, and CR will become a paragraph contents, thus the paragraphs won't be empty (they will include one invisible character, which is e.g. possible to find using \x0D or [:control:] regex; also simple navigating through the document using right arrow key would show that there is one character - the cursor will not travel to th next paragraph immediately after it reached the end of current paragraph, and one more keypress will be needed).
FTR: this normal behavior can be also reproduced on Windows, if you open a CRLF text file using "Text - Choose Encoding" filter, and choose "LF" as paragraph break.