To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=75214


User sba changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |DUPLICATE
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Thu Mar  8 16:47:19 +0000 
2007 -------
SBA: The string inside the square brackets, is "treated differently". In this
case it is NOT  interpreted as regular expression. A good example (see list of
regular expressions) is the "^":

"[^a-s]" finds any character that is not between a and s.
"^a-s" finds the string "a-s" when it is at the beginnig of a paragraph.

In your case, the \n and \t INSIDE the brackets are NOT interpreted as hard line
break but as "find the letters n and t". 

Clarification:
For Search Strings:
\n = "New Line" = A hard Line break, entered with <Shift>+>Enter>. With
"nonprinting characters visible", it looks like a tiny broken arrow, just like
the one on the "Enter" Key on regular Computer Keyboards.
$ = "Paragraph End", entered with <Enter>. With "nonprinting characters
visible", it looks like a "mirrored P" with two vertical lines.

For replace strings:
\n in "Replace Feld" adds a Paragraph break. 

I admit that this is not very intuiitive. This is good old (OK, very old) code.
I know that the regular expression handling already triggerd a nice pile of
enhancement or feature requests. A search for "Regular Ex" OR Regex" AND "State=
NOT closed" brings up 30 results (Defects, enhancements and features). Most of
them have target OOo Later, thus developers from the community shall feel free
very welcome to make things better in this area.

I regard issue 46165 as a good "survivor" for the problem with combining regular
expressions.
I put the findings here into that one and put kpalagin on c/c of that one.

Set to duplicate. 


*** This issue has been marked as a duplicate of 46165 ***

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to