https://bugs.documentfoundation.org/show_bug.cgi?id=128999
Justin L <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86-64 (AMD64) |All Version|6.2.6.2 release |Inherited From OOo Severity|normal |minor Priority|medium |lowest Summary|EDITING:find&replace |EDITING:regex find&replace |replaces "\n" in document |splits into two paragraphs |with newline formatting |when a back-reference | |contains a literal "\n" OS|Windows (All) |All --- Comment #8 from Justin L <[email protected]> --- This has nothing to do with finding or replacing font type. That is irrelevant. This 'bug' is inherited from OOo. Who puts literal '\n' in their documents, and then replaces them with back references? Plus, the entire workflow presented here is entirely fictional. This kind of 'formatting' should be either handled by styles, or by a non-regex search. Extremely minor and unimportant. repro 26.8 Steps to reproduce: -open 'testregex.odt' from comment 2 -regex search for .+ -replace with $0 I thought perhaps this could be solved with rReplaceStr = sBuff.makeStringAndClear().replaceAll("\\n", "\\\n"); but then it turns the \n into a linefeed instead of a new paragraph. -- You are receiving this mail because: You are the assignee for the bug.
