<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Find/replace non-printing characters easily"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=31480#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Find/replace non-printing characters easily"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=31480">bug 31480</a>
from <span class="vcard"><a class="email" href="mailto:eyalroz1@gmx.com" title="Eyal Rozenberg <eyalroz1@gmx.com>"> <span class="fn">Eyal Rozenberg</span></a>
</span></b>
<pre>(In reply to Jan-Marek Glogowski from <a href="show_bug.cgi?id=31480#c24">comment #24</a>)
<span class="quote">> There is simply no way to search for newlines with an regexp.</span >
I believe you're misunderstanding... the requested feature is not applying a
regexp to the serialization of LO's representation of the document, but rather
to implement a regexp in a way in which a more complex search (e.g. using XPath
or what-not) would perform a close equivalent of what a regexp application
would in a pure textual document.
Specifically, in your example document, the regexp /Two\nThree/ would find a
match, starting before the T of Two and ending after the Three, on the next
line.
It is up to LO to make this "magic" happen.</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>