Somthing like this is a bit more robust and writes a backup just in case it destroys stuff ;-) The [^<] class works well for REs in HTML where you want to match potential multilines. There are of course edge cases where < could be valid content between tags. You deal with them with a forward lookahead ([^<]+|<(?!\s*/))* and alternation.

This sort of thing is a quick and dirty solution, the parsing modules or templating are better. 

perl -pi.bak -e 's#<\s*title\s*>([^<]+|<(?!\s*/))*<\s*/\s*title\s*>#<t
+itile>New Title</title>#i' <files>

# this will correctly parse horrid stuff like
<TiTle >
One is < two
more
stuff
</ title>
<foo>bar</foo>

[download]

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

In reply to Re: Re: Rename html page titles by tachyon
in thread Rename html page titles by Concept99

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.