[Libreoffice-bugs] [Bug 53290] New: [Find and replace] Backreference is not evaluated if word boundary is present in search string
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Aug 9 13:51:19 CEST 2012
https://bugs.freedesktop.org/show_bug.cgi?id=53290
Bug #: 53290
Summary: [Find and replace] Backreference is not evaluated if
word boundary is present in search string
Classification: Unclassified
Product: LibreOffice
Version: 3.5.0 release
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Libreoffice
AssignedTo: libreoffice-bugs at lists.freedesktop.org
ReportedBy: miniopl at poczta.onet.pl
Backreference ($n) in "replace" is not evaluated if word boundary symbol is
present in "search" string.
Steps to reproduce:
1. Open new document, write to it:
#v+
what whatever what whatever
what whatever what
#v-
(there is no space after final word)
2. Open "Search and replace" dialog. Check "regular expression" in "More
options".
3. In "Search" field write:
(what)\>
4. In "Replace" field write:
$1ever
5. Hit "Replace all"
Expected output:
#v+
whatever whatever whatever whatever
whatever whatever whatever
#v-
Actual output depends on application.
1. Calc gets it all correct (as expected).
2. Impress and Draw gets it all wrong:
#v+
$1ever whatever $1ever whatever
$1ever whatever $1ever
#v-
3. Writer gets it half-correct - backreference is evaluated only if matched
word is last word in line:
#v+
$1ever whatever $1ever whatever
$1ever whatever whatever
#v-
I was able to reproduce this behavior on:
1. LibreOffice 3.6 on Windows 7, i386 (only Writer tested)
2. LibreOffice 3.5.5 on Debian, amd64
3. LibreOffice 3.5.0 on Windows 7, i386 (only Writer tested) (build id:
7e68ba2-a744ebf-1f241b7-c506db1-7d53735)
I can not check it on any earlier version of LO, but this is possible
regression.
Best regards
Mirosław Zalewski
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Libreoffice-bugs
mailing list