<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - EDITING: find/replace regular expressions: \n has 2 meanings, it shouldn't"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108256#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - EDITING: find/replace regular expressions: \n has 2 meanings, it shouldn't"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108256">bug 108256</a>
from <span class="vcard"><a class="email" href="mailto:akerblom@flopcat.org" title="akerblom@flopcat.org">akerblom@flopcat.org</a>
</span></b>
<pre>2 have occurred just in my household:
1- my daughter wanted to cut and paste song lyrics into a story she was
writing, but in paragraph form. So she needed to at the end of every line hand
delete the paragraph break and replace it with a space. It was a very long
song.
2- I have hundreds/thousands of old emails from back when they were sent only
in plain text format. When you would reply, the paragraphs would be
word-wrapped at 76 characters (or so) and on each new line a "> " would be
prepended. We'd format new paragraphs by having 2 carriage returns.
Preserving old emails into a document requires replacing all those single
carriage returns with spaces and the double carriage returns with single
carriage returns. A lot of reformatting.
Basically - this is something you run into with reformatting text obtained from
elsewhere. Also, it would be helpful for bringing text from or to a
spreadsheet format.
Clearly it is not a theoretical problem. In fact, a quick google search finds
complaints about this going back 5-6 years, with some painful workarounds. But
really this should just be in the already available find/replace feature.
Noone should have to cut and paste thier LibreWriter doc into MSWord to be able
to replace on <CR>.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>