I'm having a problem using the URI::Find module to process a mixture of plain text and HTML code.

The perldoc suggests using the following code:

use CGI qw(escapeHTML); $text = "<pre>\n" . escapeHTML($text) . "</pre>\n"; my $finder = URI::Find->new( sub { my($uri, $orig_uri) = @_; return qq|<a href="$uri">$orig_uri</ +a>|; }); $finder->find(\$text);

This works beautifully when I'm processing plain text input, however the callback doesn't have any context so it cannot avoid modifying the following badly:

<a href="http://foo.com/">foo</a>

This is transformed even though I don't need it to be.

Short of trying to heuristically detect whether I'm processing HTML or plain text is there another module I could use to insert hyperlinks around URIs which are not already linked ?

Steve
--

In reply to Using URI::Find with HTML by skx

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.