Hitch - somehow the email you sent the mail from is non-deliverable. I'm
cc'ing notetab [NTB] main list in case you are not subscribed to the
Regards ... Alec (buralex@gmail& WinLiveMess - alec.m.burgess@skype)
On Wed, 17 Apr 2013 16:25:02 -0400 Alec Burgess
> said (in part):
> Hi Hitch:
> You accidentally (I assume) sent this off-list to just me. I'm cc'ing
> the clips list. As a rule of thumb we usually discuss regexp on the
> clips list but its not a biggie either way.
> Regexp Buddy has the option to specify that [Dot matches newline]. The
> Notetab default is to have Dot *NOT* match newline. You can force this
> by using (?s) as the beginning of your Search regexp.
> ie: (?s)<italic span>(.*?)</span>
> If you look at the [Create] tab in Regexp Buddy it makes it clear how
> this option works.
> Regards ... Alec (buralex@gmail& WinLiveMess - alec.m.burgess@skype)
> On 2013-04-17 16:03, kahitch@... wrote:
>> Noob here, although been using NTP (Pro) for some years now. I have
>> a question that is driving me nuts, and I don't know if this group is
>> the best place, or I should go over to clips, but, I've had this regex:
>> Search:<italic span>(.*?)</span> Replace:<i>$1</i>
>> To replace spans that were created wrapped around text with an italic
>> style, instead of proper italics tags, or a named CSS style, for
>> messy Word docs being extracted to HTML and thence to XHTML to make
>> Now, I have used this without incident for some years. Suddenly, it
>> won't work if in the text (.*?) between the spans, there's a line
>> break/non-printing char, i.e., a P or n or l.
>> I have regexbuddy, to help me cheat when needed, but can't seem to
>> wrap my head around WHY this suddenly stopped working. Nor can I
>> remember how to make NTP unwrap ALL the lines without merging all the
>> paragraphs, which at least are correctly wrapped with opening and
>> closing p tags, but as I said, the non-printing chars in the text
>> *between* the spans seems to be bollixing me.
>> If anyone has any thoughts, I'd appreciate it. I feel stupid asking
>> this, but this SHOULD be a minor problem, and it usually is, but
>> somehow, this one is not flying; was there a change to the PCRE for
>> --- In email@example.com, Alec Burgess<buralex@...> wrote:
>>> View - Show non-printing characters (Shift+F12)
>>> Worth adding to your toolbar :-)