comment on

Hi guys,

Thank you for your quicky replies. I think I found what's wrong inside xml document. It seems that only if a link contains character '&' then the parser reports an error.

For example, <link r:resource="http://www.urbancinefile.com.au/home/article_view.asp?Article_ID=3801&Section=Reviews"/>

As I need to read <link/> elements one by one and compare the attribute value with user's input, my new question is, how can I overcome this '&' problem? I have tried to use '\' before '&' but it doesn't work.

Thanks again,

sub topic {
my $count = 0;
my ($twig, $topic) = @_;
$links{$_->att('r:resource')} = $_ for $topic->children('link');
foreach my $key (keys %links){
if ($key =~ /$q/i){
print "

", $topic->att('r:id'), "

\n";
$count++;
}
last if ($count == 1); #if keywords were found in one link, we don't need to check the others in the same node, because we aim to output parent category only.
}
print "\n";
$twig->purge;
%links = (); #reset the hash for next time use
}

Nan

In reply to Re^2: Why XML not well formed? by nan
in thread Why XML not well formed? by nan

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks