Parsing HTML with regexps is error prone. HTML::Parser, HTML::TreeBuilder, etc are great tools. Here is a short example: 
my $str = q{
<span id=editArea name="whatever">
bla bla a bunch of html and text that will change from file to file
</span>
};

use HTML::TreeBuilder;

my $t = HTML::TreeBuilder->new_from_content($str);

foreach ($t->look_down('_tag', 'span')) {
    next if $_->attr('id') ne 'editArea' || $_->attr('name') ne 'whate
+ver';
    $_->delete_content;
    $_->push_content('this is some replacement text');    
}

print $t->as_HTML;
$t->delete;

[download]

gav^

In reply to Re: Open, Find, Replace, Rewrite, Close.. Advice on best path to take by gav^
in thread Open, Find, Replace, Rewrite, Close.. Advice on best path to take by NightTrainX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.