<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi, Fred.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hmmm … I understand your point, but am not sure I would <i>entirely</i> agree with the reasoning. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes, FrameMaker (and other programs like Word) do put in additional information besides the EOP glyph itself.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br>But, this is a relatively commonly used/desired function – certainly in simple text editors – to replace an EOP with other characters (perhaps including an EOP). For example, to “join” multiple lines together, or to do what Klaus mentions.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes, FM is <i>not</i> just a simple text editor, which is why I see your reasoning to not call it a bug.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>But I think it would be good to define exactly what regular expression matching is supposed to do with EOP markers then (or have a special mechanism to identify <i>and</i> use an EOP more effectively perhaps?)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Z<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com] <b>On Behalf Of </b>Fred Ridder<br><b>Sent:</b> Monday, July 07, 2014 8:02 AM<br><b>To:</b> frame@daube.ch; framers@lists.frameusers.com<br><b>Subject:</b> RE: FM12: Quirks in Find/replace using RegEx (Perl)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Calibri","sans-serif"'>No, I don't think it is a bug. <br>And end-of-paragraph mark is not a simple glyph; it has properties and attributes associated with it (e.g. a paragraph tag, the formatting associated with that paragraph tag, and any overrides to the standard formatting for the tag). <br>You can find an EOP as if it were a simple glyph because they do have a common fundamental property (i.e. denoting the end of a paragraph). <br>But you cannot effectively insert a new EOP in a replace string because there is no way to associate any of the other properties with the new mark. <br>Finding an EOP and replacing it with itself, on the other hand, is a valid operation because the found mark has a full complement of paragraph properties.<br><br>-Fred Ridder<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>> From: <a href="mailto:frame@daube.ch">frame@daube.ch</a><br>> To: <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br>> Date: Mon, 7 Jul 2014 15:48:17 +0200<br>> Subject: FM12: Quirks in Find/replace using RegEx (Perl)<br>> <br>> Friends of FramMaker, please judge.<br>> <br>> I want to find incorrectly ended paragraphs (missing punctuation).<br>> For example the following 4 lines are paragraphs, the first 2 correct,<br>> the next two incorrect:<br>> <br>> This is the first paragraph!<br>> And this is the second one.<br>> And here a third<br>> And a fourth one:<br>> <br>> RegEx Find/Replace with these settings:<br>> Find: ([^\.!?])\n<br>> Repl: $1.\n<br>> Result: find is correct, replacement is n instead of paragraph end<br>> With repl = $1.\r replacement is a forced newline; correct, but not wanted.<br>> <br>> Find: ([^\.!?])(\n)<br>> Repl: $1.$2<br>> This creates a correct replacement!<br>> <br>> IMHO the behaviour of not honoring \n as an 'end of paragraph' for the replacement is <br>> a bug. Do You agree?<br>> <br>> Klaus Daube<o:p></o:p></span></p></div></div></div></body></html>