<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#336666">
<font face="Verdana">There's no reason the plain-text replacement
can't add EOPs .. just need a code to do that. You can do that
with a regular search/replace by searching on "\p" and replacing
with "\p\p". The "\n" is a forced return in the non-regex UI. It
should at least do the same .. not an "n".<br>
<br>
...scott<br>
<br>
<br>
</font>
<div class="moz-cite-prefix">On 7/7/14 6:07 PM, Fred Ridder wrote:<br>
</div>
<blockquote cite="mid:SNT150-W95B3B96CB00B709EBA5611BA0C0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">But if there is no practical way for a plain
text-oriented tool to insert a *proper* EOP, the only way to
make Frame's overall Find/Replace behavior consistent would be
to forbid searching for EOPs. And that would be a *real*
shortcoming IMO. Kind of like throwing out the baby with the
bathwater...<br>
<br>
-Fred<br>
<br>
<div>
<hr id="stopSpelling">Date: Mon, 7 Jul 2014 16:57:03 -0700<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:sp10@leximation.com">sp10@leximation.com</a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br>
Subject: Re: FM12: Quirks in Find/replace using RegEx (Perl)<br>
<br>
<div class="ecxmoz-cite-prefix"><font face="Verdana">I dunno.
I just don't like the fact that "\n" will match on a line
end (of some type), while it replaces as an "n" .. that's
not right.<br>
<br>
...scott<br>
<br>
</font> On 7/7/14 4:52 PM, Syed Zaeem Hosain (<a
moz-do-not-send="true" class="ecxmoz-txt-link-abbreviated"
href="mailto:Syed.Hosain@aeris.net">Syed.Hosain@aeris.net</a>)
wrote:<br>
</div>
<blockquote
cite="mid:B4C122ABC82F8744A7E552CA009BA22A1A7A370E20@EX-BE-019-SFO.shared.themessagecenter.com">
<style><!--
.ExternalClass .ecxshape {
}
--></style>
<style><!--
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:blue;
text-decoration:underline;
}
.ExternalClass span.ecxMsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}
.ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxmsonormal, .ExternalClass li.ecxmsonormal, .ExternalClass div.ecxmsonormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass p.ecxmsochpdefault, .ExternalClass li.ecxmsochpdefault, .ExternalClass div.ecxmsochpdefault {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass span.ecxmsohyperlink {
}
.ExternalClass span.ecxmsohyperlinkfollowed {
}
.ExternalClass span.ecxemailstyle18 {
}
.ExternalClass p.ecxmsonormal1, .ExternalClass li.ecxmsonormal1, .ExternalClass div.ecxmsonormal1 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass span.ecxmsohyperlink1 {
color:#0563C1;
text-decoration:underline;
}
.ExternalClass span.ecxmsohyperlinkfollowed1 {
color:#954F72;
text-decoration:underline;
}
.ExternalClass span.ecxemailstyle181 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}
.ExternalClass p.ecxmsochpdefault1, .ExternalClass li.ecxmsochpdefault1, .ExternalClass div.ecxmsochpdefault1 {
font-size:10.0pt;
font-family:"Times New Roman","serif";
}
.ExternalClass span.ecxEmailStyle28 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}
.ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}
.ExternalClass div.ecxWordSection1 {
}
--></style>
<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Yeah
… I have to admit that I can’t argue with you on this
too much. </span><span
style="font-size:11.0pt;font-family:Wingdings;color:#1F497D;">J</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">
Because, there isn’t a simple “this is the right way”
to do the EOP insertions.</span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Although
… <i>maybe</i> … Word stands a slightly better chance
because of its “Normal” paragraph that <i>could</i>
get applied by default. Of course, as you note, this
could cause a mess with documents whose paragraphs
have already been changed to some other paragraph
format, etc.</span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Z</span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="ecxMsoNormal"><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";">
Fred Ridder [<a moz-do-not-send="true"
class="ecxmoz-txt-link-freetext"
href="mailto:docudoc@hotmail.com">mailto:docudoc@hotmail.com</a>]
<br>
<b>Sent:</b> Monday, July 07, 2014 10:18 AM<br>
<b>To:</b> Syed Zaeem Hosain (<a
moz-do-not-send="true"
class="ecxmoz-txt-link-abbreviated"
href="mailto:Syed.Hosain@aeris.net">Syed.Hosain@aeris.net</a>);
<a moz-do-not-send="true"
class="ecxmoz-txt-link-abbreviated"
href="mailto:frame@daube.ch">frame@daube.ch</a>;
<a moz-do-not-send="true"
class="ecxmoz-txt-link-abbreviated"
href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br>
<b>Subject:</b> RE: FM12: Quirks in Find/replace
using RegEx (Perl)</span></p>
</div>
</div>
<p class="ecxMsoNormal"> </p>
<div>
<p class="ecxMsoNormal" style=""><span
style="font-family:"Calibri","sans-serif";">Don't
get me wrong. I'm not saying that it wouldn't be
*useful* to be able to insert a new EOP. But the
reality is that in either Word or FrameMaker (and I
assume in other word processing applications) it is
problematic because EOP is not a simple character.
Regular expressions are designed to work with
arbitrary strings of simple characters. They were
never intended to handle characters that have
formatting or page layout properties embedded in
them. If a regular expression *were* able to insert
a new EOP, what formatting should apply to it? Since
regular expressions don't know about formatting, the
only practical answer is the lowest level default
formatting. But in any properly designed word
processor document (i.e., one that uses styles) that
default is going to be *wrong* in >99% of cases
and require further, manual attention from the
author, which really defeats the benefit of being
able to use a regular expression replacement. A
simple text editor is a completely different
situation because there really is nothing special
about an EOP. <br>
<br>
I think the real point is that in Klaus' case the
analysis of the task was slightly flawed. To fix his
punctuation issue, what he really wants to do is
insert a period (full stop) between the current
unpunctuated text and the existing EOP, which is
exactly what his second regular expression does.
There really is no reason to delete the existing EOP
(and all the "magic" embedded in it) and replace it
with a brand-new, untagged EOP that would require
his manual attention to tag and/or format.
FrameMaker's behavior of not allowing this saves the
user from having to do a lot of after-the-fact
cleanup. <br>
<br>
FrameMaker's regular expressions let you find EOPs
without issue, and lets you reuse them. What they
don't let you do is try to create a new one where
there is insufficient information in the found text
string(s) to do that operation without making a
mess.<br>
<br>
-Fred</span></p>
<div>
<div class="ecxMsoNormal" style="text-align:center;"
align="center"><span
style="font-family:"Calibri","sans-serif";">
<hr id="ecxstopSpelling" align="center" size="3"
width="100%"></span></div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>