[Htmlparser-developer] RE: [Htmlparser-user] Integration Release 1.3-20030323 is out

[Marc N. <ma...@ke...>]

By the way, I've entered the OOM exception as a bug (#709152), along =
with a simple program that reproduces it.

Marc

-----Original Message-----
From: Marc Novakowski=20
Sent: Monday, March 24, 2003 3:23 PM
To: htm...@li...
Subject: RE: [Htmlparser-user] Integration Release 1.3-20030323 is out


Somik,

Thanks for fixing 702614!  Unfortunately I can't seem to get the latest =
build to work.  It's throwing an OOM exception in my own code when using =
the NodeIterator returned by parser.elements().  I'm looking into this =
to make sure I'm not doing something stupid in my code.  However, the =
library seems to be acting differently than previous releases even =
out-of-the-box.  For example, the following used to return a list of the =
links on Yahoo (in the 0302 release):

java -jar ./htmlparser.jar http://www.yahoo.com -l

In the 0323 release, however, it returns nothing.

Marc

-----Original Message-----
From: Somik Raha [mailto:so...@ya...]
Sent: Sunday, March 23, 2003 5:24 PM
To: HTMLParser Announcement List; HTMLParser User List; HTMLParser
Developer List
Subject: [Htmlparser-user] Integration Release 1.3-20030323 is out


Hi Folks,
    This week's integration release has two important fixes :

Integration build 1.3 - 20030323
--------------------------------
[1] Fixed bug 702547 - single quotes parsed more robustly now
[2] Fixed bug 702614 - empty tags handled correctly now. Tag now has a
method isEmptyXmlTag().

#2 refers to tags like <tag/>.

Thanks to Joe Robbins for a fine bug report that helped in putting in =
the
fix for #1 faster. Thanks also to Marc Novakowski for the other report.

Thanks are also due to Huang-Chun Yu for uncovering a serious bug with =
the
script scanning mechanism. The parser can currently handle script tags =
like
:

<script>
<!--
    code here
-->
</script>

But when the tags are like:
<script>
    code here
</script>

the parser is unable to identify the code and treats it like regular =
tags.
Such pages are quite widespread and ought to be supported. I was curious =
if
anyone has ideas on solving this - given the existing design - fresh =
ideas
often lead to a better perspective. If you have some ideas, feel free to
join the developer list
(http://lists.sourceforge.net/lists/listinfo/htmlparser-developer) and =
post.

Regards,
Somik



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!=20
Get cracking and register here for some mind boggling fun and=20
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Htmlparser-user mailing list
Htm...@li...
https://lists.sourceforge.net/lists/listinfo/htmlparser-user


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Htmlparser-user mailing list
Htm...@li...
https://lists.sourceforge.net/lists/listinfo/htmlparser-user