blocks|key|3249463|text|将The+validator.nu+HTML+Parser添加到您的列表中，它是HTML5解析算法在Java语言中的一个实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3249464|从好的方面来说，它是专门为匹配HTML5而设计的，并且是HTML5验证器的核心，因此很有可能匹配未来浏览器的解析行为，达到非常高的准确度。|3249465|不利的一面是，没有浏览器的遗留解析完全像这样工作，而且HTML5仍处于草案阶段，可能会发生变化。|3249466|在实践中，这样的问题只影响晦涩难懂的角落情况，并且对于所有实际目的来说，都是一个优秀的解析器。|3249467|entityMap|0|LINK|mutability|MUTABLE|url|http://about.validator.nu/htmlparser/^0|1|S|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

Add <a href="http://about.validator.nu/htmlparser/" rel="noreferrer">The validator.nu HTML Parser</a>, an implementation of the HTML5 parsing algorithm in Java, to your list. 

On the plus side, it's specifically designed to match HTML5, and at the heart of the HTML5 validator, so highly likely to match future browser's parsing behaviour to a very high degree of accuracy.

On the minus side, no browsers' legacy parsing works exactly like this, and as HTML5 is still in draft, subject to change. 

In practice, such problems only affect obscure corner cases, and is for all practical purposes, an excellent parser.

blocks|key|3035198|text|This+article比较了以下解析器的某些方面：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3035199|3035200|NekoHTML|unordered-list-item|3035201|JTidy|3035202|TagSoup|3035203|HtmlCleaner|3035204|3035205|这绝不是一个完整的总结，它是从2008年开始的。但你可能会发现它很有帮助。|3035206|entityMap|0|LINK|mutability|MUTABLE|url|http://www.benmccann.com/blog/java-html-parsing-library-comparison/^0|0|C|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|13|8|@]|9|@]|C|$]]|$1|H|3|I|5|G|7|14|8|@]|9|@]|C|$]]|$1|J|3|K|5|G|7|15|8|@]|9|@]|C|$]]|$1|L|3|M|5|G|7|16|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

<a href="http://www.benmccann.com/blog/java-html-parsing-library-comparison/" rel="nofollow noreferrer">This article</a> compares certain aspects of the following parsers:

<ul>
<li>NekoHTML</li>
<li>JTidy</li>
<li>TagSoup</li>
<li>HtmlCleaner</li>
</ul>

It is by no means a complete summary, and it is from 2008. But you may find it helpful.

blocks|key|303372|text|我发现Jericho+HTML+Parser写得非常好，保持最新(许多解析器都不是)，没有依赖性，并且易于使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|303373|entityMap|0|LINK|mutability|MUTABLE|url|http://jericho.htmlparser.net/docs/index.html^0|3|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I found <a href="http://jericho.htmlparser.net/docs/index.html" rel="nofollow noreferrer">Jericho</a> HTML Parser to be very well written, kept up to date (which many of the parsers are not), no dependencies, and easy to use.

blocks|key|3249503|text|一般信息|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3249504|几乎所有已知的HTML解析器都实现了W3C+DOM+API+(+JAXP+API的一部分，用于XML处理的Java+API+)，并返回一个可供JAXP+API直接使用的org.w3c.dom.Document。主要的区别通常在于所讨论的解析器的特性。大多数解析器在某种程度上对非格式的超文本标记语言(“标签汤”)都是宽宏大量的，比如JTidy、NekoHTML、TagSoup和HtmlCleaner。您通常使用这种HTML解析器来“整理”HTML源代码(例如，将HTML有效的 替换为XML有效的<br+/>)，这样您就可以使用W3C+DOM和JAXP+API以“通常的方式”遍历它。|offset|length|style|CODE|3249505|唯一脱颖而出的是HtmlUnit和Jsoup。|3249506|HtmlUnit|3249507|HtmlUnit提供了一个完全自带的应用程序接口，它可以让你以编程的方式像act浏览器一样工作。例如，输入表单值、单击元素、调用JavaScript等。它不仅仅是一个HTML解析器。它是一个真正的“无GUI的real浏览器”和HTML单元测试工具。|3249508|Jsoup|3249509|Jsoup还提供了一个完全自己的应用程序接口。它为您提供了使用jQuery-like+CSS+selectors选择元素的可能性，并提供了一个灵活的API来遍历HTML+DOM树以获取感兴趣的元素。|3249510|特别是对HTML+DOM树的遍历是Jsoup的主要优点。使用过org.w3c.dom.Document的人都知道使用冗长的NodeList和Node+API遍历DOM是多么痛苦。诚然，XPath让生活变得更容易，但这仍然是另一条学习曲线，最终可能仍然很冗长。|3249511|这里有一个例子，它使用一个“普通的”W3C+DOM解析器，比如JTidy和XPath来提取问题的第一段和所有回答者的名字(我使用XPath是因为没有它，收集感兴趣的信息所需的代码将增长10倍，而不需要编写实用程序/助手方法)。|3249512|String+url+=+"http://stackoverflow.com/questions/3152138";
Document+document+=+new+Tidy().parseDOM(new+URL(url).openStream(),+null);
XPath+xpath+=+XPathFactory.newInstance().newXPath();
++
Node+question+=+(Node)+xpath.compile("//*[@id='question']//*[contains(@class,'post-text')]//p[1]").evaluate(document,+XPathConstants.NODE);
System.out.println("Question:+"+%2B+question.getFirstChild().getNodeValue());

NodeList+answerers+=+(NodeList)+xpath.compile("//*[@id='answers']//*[contains(@class,'user-details')]//a[1]").evaluate(document,+XPathConstants.NODESET);
for+(int+i+=+0;+i+<+answerers.getLength();+i%2B%2B)+{
++++System.out.println("Answerer:+"+%2B+answerers.item(i).getFirstChild().getNodeValue());
}|code-block|syntax|javascript|3249513|下面是一个如何使用Jsoup执行完全相同的操作的示例：|3249514|String+url+=+"http://stackoverflow.com/questions/3152138";
Document+document+=+Jsoup.connect(url).get();

Element+question+=+document.select("#question+.post-text+p").first();
System.out.println("Question:+"+%2B+question.text());

Elements+answerers+=+document.select("#answers+.user-details+a");
for+(Element+answerer+:+answerers)+{
++++System.out.println("Answerer:+"+%2B+answerer.text());
}|3249515|你看到区别了吗？它不仅代码更少，而且如果你已经有一定的CSS选择器的经验(例如，开发网站和/或使用jQuery)，它也是相对容易掌握的。|3249516|摘要|3249517|现在，每种方法的利弊应该已经足够清楚了。如果只想使用标准JAXP+API遍历它，那么使用前面提到的一组解析器。他们中有相当多的a+lot。选择哪一个取决于它提供的功能(如何让HTML清理变得容易？是否有一些侦听器/拦截器和特定于标签的清理器？)以及库的健壮性(多长时间更新/维护/修复一次？)。如果你喜欢对超文本标记语言进行单元测试，那么HtmlUnit是个不错的选择。如果您希望从HTML中提取特定的数据(这通常是现实世界的需求)，那么Jsoup就是最佳选择。|3249518|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/package-summary.html|1|http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/Document.html|2|http://jtidy.sourceforge.net/|3|http://nekohtml.sourceforge.net/|4|http://home.ccil.org/%257Ecowan/XML/tagsoup/|5|http://htmlcleaner.sourceforge.net/|6|http://htmlunit.sourceforge.net/|7|http://jsoup.org/|8|9|10|http://jquery.com/|11|http://www.w3.org/TR/css3-selectors/|12|http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/NodeList.html|13|http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/Node.html|14|http://docs.oracle.com/javase/6/docs/api/javax/xml/xpath/XPath.html|15|http://java-source.net/open-source/html-parsers^0|0|2C|K|6N|4|70|6|I|B|0|2C|K|1|4M|5|2|4S|8|3|51|7|4|59|B|5|0|8|8|6|H|5|7|0|0|0|8|8|0|0|0|5|9|V|6|A|17|D|B|0|V|K|1P|8|1Y|4|2K|5|1P|8|C|1Y|4|D|2K|5|E|0|0|0|0|0|0|0|1R|5|F|0^^$0|@$1|2|3|4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2B|8|@$D|2C|E|2D|F|G]|$D|2E|E|2F|F|G]|$D|2G|E|2H|F|G]]|9|@$D|2I|E|2J|1|2K]|$D|2L|E|2M|1|2N]|$D|2O|E|2P|1|2Q]|$D|2R|E|2S|1|2T]|$D|2U|E|2V|1|2W]|$D|2X|E|2Y|1|2Z]]|A|$]]|$1|H|3|I|5|6|7|30|8|@]|9|@$D|31|E|32|1|33]|$D|34|E|35|1|36]]|A|$]]|$1|J|3|K|5|6|7|37|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|38|8|@]|9|@$D|39|E|3A|1|3B]]|A|$]]|$1|N|3|O|5|6|7|3C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|3D|8|@]|9|@$D|3E|E|3F|1|3G]|$D|3H|E|3I|1|3J]|$D|3K|E|3L|1|3M]]|A|$]]|$1|R|3|S|5|6|7|3N|8|@$D|3O|E|3P|F|G]|$D|3Q|E|3R|F|G]|$D|3S|E|3T|F|G]|$D|3U|E|3V|F|G]]|9|@$D|3W|E|3X|1|3Y]|$D|3Z|E|40|1|41]|$D|42|E|43|1|44]]|A|$]]|$1|T|3|U|5|6|7|45|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|46|8|@]|9|@]|A|$Y|Z]]|$1|10|3|11|5|6|7|47|8|@]|9|@]|A|$]]|$1|12|3|13|5|X|7|48|8|@]|9|@]|A|$Y|Z]]|$1|14|3|15|5|6|7|49|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|4A|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|4B|8|@]|9|@$D|4C|E|4D|1|4E]]|A|$]]|$1|1A|3|-4|5|6|7|4F|8|@]|9|@]|A|$]]]|1B|$1C|$5|1D|1E|1F|A|$1G|1H]]|1I|$5|1D|1E|1F|A|$1G|1J]]|1K|$5|1D|1E|1F|A|$1G|1L]]|1M|$5|1D|1E|1F|A|$1G|1N]]|1O|$5|1D|1E|1F|A|$1G|1P]]|1Q|$5|1D|1E|1F|A|$1G|1R]]|1S|$5|1D|1E|1F|A|$1G|1T]]|1U|$5|1D|1E|1F|A|$1G|1V]]|1W|$5|1D|1E|1F|A|$1G|1T]]|1X|$5|1D|1E|1F|A|$1G|1V]]|1Y|$5|1D|1E|1F|A|$1G|1Z]]|20|$5|1D|1E|1F|A|$1G|21]]|22|$5|1D|1E|1F|A|$1G|23]]|24|$5|1D|1E|1F|A|$1G|25]]|26|$5|1D|1E|1F|A|$1G|27]]|28|$5|1D|1E|1F|A|$1G|29]]]]

<h3>General</h3>
Almost all known HTML parsers implements the <a href="http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/package-summary.html" rel="noreferrer">W3C DOM API</a> (part of the JAXP API, Java API for XML processing) and gives you a <a href="http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/Document.html" rel="noreferrer"><code>org.w3c.dom.Document</code></a> back which is ready for direct use by JAXP API. The major differences are usually to be found in the features of the parser in question. Most parsers are to a certain degree forgiving and lenient with non-wellformed HTML (&quot;tagsoup&quot;), like <a href="http://jtidy.sourceforge.net/" rel="noreferrer">JTidy</a>, <a href="http://nekohtml.sourceforge.net" rel="noreferrer">NekoHTML</a>, <a href="http://home.ccil.org/%7Ecowan/XML/tagsoup/" rel="noreferrer">TagSoup</a> and <a href="http://htmlcleaner.sourceforge.net/" rel="noreferrer">HtmlCleaner</a>. You usually use this kind of HTML parsers to &quot;tidy&quot; the HTML source (e.g. replacing the HTML-valid <code>&lt;br&gt;</code> by a XML-valid <code>&lt;br /&gt;</code>), so that you can traverse it &quot;the usual way&quot; using the W3C DOM and JAXP API.
The only ones which jumps out are <a href="http://htmlunit.sourceforge.net/" rel="noreferrer">HtmlUnit</a> and <a href="http://jsoup.org/" rel="noreferrer">Jsoup</a>.
<h3>HtmlUnit</h3>
<a href="http://htmlunit.sourceforge.net/" rel="noreferrer">HtmlUnit</a> provides a completely own API which gives you the possibility to act like a webbrowser programmatically. I.e. enter form values, click elements, invoke JavaScript, etcetera. It's much more than alone a HTML parser. It's a real &quot;GUI-less webbrowser&quot; and HTML unit testing tool.
<h3>Jsoup</h3>
<a href="http://jsoup.org/" rel="noreferrer">Jsoup</a> also provides a completely own API. It gives you the possibility to select elements using <a href="http://jquery.com" rel="noreferrer">jQuery</a>-like <a href="http://www.w3.org/TR/css3-selectors/" rel="noreferrer">CSS selectors</a> and provides a slick API to traverse the HTML DOM tree to get the elements of interest.
Particularly the traversing of the HTML DOM tree is the major strength of Jsoup. Ones who have worked with <code>org.w3c.dom.Document</code> know what a hell of pain it is to traverse the DOM using the verbose <a href="http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/NodeList.html" rel="noreferrer"><code>NodeList</code></a> and <a href="http://docs.oracle.com/javase/6/docs/api/org/w3c/dom/Node.html" rel="noreferrer"><code>Node</code></a> APIs. True, <a href="http://docs.oracle.com/javase/6/docs/api/javax/xml/xpath/XPath.html" rel="noreferrer"><code>XPath</code></a> makes the life easier, but still, it's another learning curve and it can end up to be still verbose.
Here's an example which uses a &quot;plain&quot; W3C DOM parser like JTidy in combination with XPath to extract the first paragraph of your question and the names of all answerers (I am using XPath since without it, the code needed to gather the information of interest would otherwise grow up 10 times as big, without writing utility/helper methods).
<pre><code>String url = &quot;http://stackoverflow.com/questions/3152138&quot;;
Document document = new Tidy().parseDOM(new URL(url).openStream(), null);
XPath xpath = XPathFactory.newInstance().newXPath();
 
Node question = (Node) xpath.compile(&quot;//*[@id='question']//*[contains(@class,'post-text')]//p[1]&quot;).evaluate(document, XPathConstants.NODE);
System.out.println(&quot;Question: &quot; + question.getFirstChild().getNodeValue());

NodeList answerers = (NodeList) xpath.compile(&quot;//*[@id='answers']//*[contains(@class,'user-details')]//a[1]&quot;).evaluate(document, XPathConstants.NODESET);
for (int i = 0; i &lt; answerers.getLength(); i++) {
 System.out.println(&quot;Answerer: &quot; + answerers.item(i).getFirstChild().getNodeValue());
}
</code></pre>
And here's an example how to do exactly the same with Jsoup:
<pre><code>String url = &quot;http://stackoverflow.com/questions/3152138&quot;;
Document document = Jsoup.connect(url).get();

Element question = document.select(&quot;#question .post-text p&quot;).first();
System.out.println(&quot;Question: &quot; + question.text());

Elements answerers = document.select(&quot;#answers .user-details a&quot;);
for (Element answerer : answerers) {
 System.out.println(&quot;Answerer: &quot; + answerer.text());
}
</code></pre>
Do you see the difference? It's not only less code, but Jsoup is also relatively easy to grasp if you already have moderate experience with CSS selectors (by e.g. developing websites and/or using jQuery).
<h3>Summary</h3>
The pros and cons of each should be clear enough now. If you just want to use the standard JAXP API to traverse it, then go for the first mentioned group of parsers. There are pretty <a href="http://java-source.net/open-source/html-parsers" rel="noreferrer">a lot</a> of them. Which one to choose depends on the features it provides (how is HTML cleaning made easy for you? are there some listeners/interceptors and tag-specific cleaners?) and the robustness of the library (how often is it updated/maintained/fixed?). If you like to unit test the HTML, then HtmlUnit is the way to go. If you like to extract specific data from the HTML (which is more than often the real world requirement), then Jsoup is the way to go.

blocks|key|3249520|text|在使用了Java中的大多数HTML解析库之后，我将添加到@MJB+answer中，其中忽略了一个巨大的利弊:在输入和输出中保留HTML的格式和不正确的解析器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3249521|也就是说，当您更改文档时，大多数解析器都会清除DOM中的空格、注释和不正确之处，特别是当它们是类似XML的库时。|3249522|是我所知道的唯一一个解析器，它允许您操作讨厌的超文本标记语言，同时保留空白格式和超文本标记语言的错误(如果有的话)。|3249523|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I'll just add to @MJB answer after working with most of the HTML parsing libraries in Java, there is a huge pro/con that is omitted: parsers that preserve the formatting and incorrectness of the HTML on input and output.

That is most parsers when you change the document will blow away the whitespace, comments, and incorrectness of the DOM particularly if they are an XML like library.

<a href="http://jericho.htmlparser.net/docs/index.html" rel="nofollow">Jericho</a> is the only parser I know that allows you to manipulate nasty HTML while preserving whitespace formatting and the incorrectness of the HTML (if there is any).

blocks|key|3249525|text|另外两个选项是HTMLCleaner和HTMLParser。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3249526|我已经尝试了这里的大多数解析器，用于我正在开发的爬虫/数据提取框架。我使用HTMLCleaner完成大部分数据提取工作。这是因为它支持一种相当现代的带有名称空间的HTMLXHTMLHTML5方言，并且它支持DOM，因此可以使用use+it+with+Java's+built+in+XPath+implementation。|3249527|与其他一些解析器相比，使用HTMLCleaner实现这一点要容易得多:例如，JSoup支持类似于DOM的接口，而不是DOM，因此需要一些组装。Jericho有一个SAX-line接口，所以需要做一些工作，虽然是Sujit+Pal+has+a+good+description+of+how+to+do+this，但最终HTMLCleaner还是工作得更好。|3249528|我还使用HTMLParser和Jericho完成一个表提取任务，它们替换了一些使用Perl的libhtml-tableextract-perl编写的代码。我使用HTMLParser过滤表的超文本标记语言，然后使用Jericho解析它。我同意MJB和Adam的评论，即Jericho在某些情况下很好，因为它保留了底层的HTML。它有一种非标准的SAX接口，所以对于XPath处理来说，HTMLCleaner更好。|3249529|在Java中解析HTML是一个令人惊讶的困难问题，因为所有的解析器似乎都很难处理某些类型的错误HTML内容。|3249530|entityMap|0|LINK|mutability|MUTABLE|url|http://htmlcleaner.sourceforge.net/|1|http://htmlparser.sourceforge.net/|2|https://stackoverflow.com/questions/9022140/using-xpath-contains-against-html-in-java|3|http://sujitpal.blogspot.tw/2009/04/xpath-over-html-using-jericho-and-jaxen.html|4|http://search.cpan.org/~msisk/HTML-TableExtract-2.11/lib/HTML/TableExtract.pm^0|7|B|0|J|A|1|0|35|1C|2|0|2X|1E|3|0|1A|P|4|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]|$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|H|3|I|5|6|7|1G|8|@]|9|@$A|1H|B|1I|1|1J]]|C|$]]|$1|J|3|K|5|6|7|1K|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]|V|$5|O|P|Q|C|$R|W]]|X|$5|O|P|Q|C|$R|Y]]|Z|$5|O|P|Q|C|$R|10]]]]

Two other options are <a href="http://htmlcleaner.sourceforge.net/" rel="nofollow noreferrer">HTMLCleaner</a> and <a href="http://htmlparser.sourceforge.net/" rel="nofollow noreferrer">HTMLParser</a>. 

I have tried most of the parsers here for a crawler / data extraction framework I have been developing. I use HTMLCleaner for the bulk of the data extraction work. This is because it supports a reasonably modern dialect of HTML, XHTML, HTML 5, with namespaces, and it supports DOM, so it is possible to <a href="https://stackoverflow.com/questions/9022140/using-xpath-contains-against-html-in-java">use it with Java's built in XPath implementation</a>. 

It's a lot easier to do this with HTMLCleaner than some of the other parsers: JSoup for example supports a DOM like interface, rather than DOM, so some assembly required. Jericho has a SAX-line interface so again it is requires some work although <a href="http://sujitpal.blogspot.tw/2009/04/xpath-over-html-using-jericho-and-jaxen.html" rel="nofollow noreferrer">Sujit Pal has a good description of how to do this</a> but in the end HTMLCleaner just worked better.

I also use HTMLParser and Jericho for a table extraction task, which replaced some code written using Perl's <a href="http://search.cpan.org/~msisk/HTML-TableExtract-2.11/lib/HTML/TableExtract.pm" rel="nofollow noreferrer">libhtml-tableextract-perl</a>. I use HTMLParser to filter the HTML for the table, then use Jericho to parse it. I agree with MJB's and Adam's comments that Jericho is good in some cases because it preserves the underlying HTML. It has a kind of non-standard SAX interface, so for XPath processing HTMLCleaner is better.

Parsing HTML in Java is a surprisingly hard problem as all the parsers seem to struggle on certain types of malformed HTML content.

Searching SO and Google, I've found that there are a few Java HTML parsers which are consistently recommended by various parties. Unfortunately it's hard to find any information on the strengths and weaknesses of the various libraries. I'm hoping that some people have spent some comparing these libraries, and can share what they've learned.

Here's what I've seen:

<ul>
<li><a href="http://jtidy.sourceforge.net/" rel="noreferrer">JTidy</a></li>
<li><a href="http://nekohtml.sourceforge.net/" rel="noreferrer">NekoHTML</a></li>
<li><a href="http://jsoup.org/" rel="noreferrer">jsoup</a></li>
<li><a href="http://home.ccil.org/~cowan/XML/tagsoup/" rel="noreferrer">TagSoup</a></li>
</ul>

And if there's a major parser that I've missed, I'd love to hear about its pros and cons as well.

Thanks!

What are the pros and cons of the leading Java HTML parsers?

单元测试

jQuery

HTML5

Java

Perl

通过搜索SO和Google，我发现有一些Java HTML解析器得到了各方的一致推荐。不幸的是，很难找到关于各种库的优点和缺点的任何信息。我希望一些人已经花了一些时间比较这些库，并可以分享他们所学到的东西。这是我所看到的：如果我错过了一个主要的解析器，我也很想听听它的优缺点。谢谢!

问领先的Java HTML解析器的优缺点是什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问领先的Java HTML解析器的优缺点是什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问领先的Java HTML解析器的优缺点是什么？
EN