<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: XhtmlValidator 0.2 released</title>
	<atom:link href="http://nutrun.com/weblog/xhtmlvalidator-02-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://nutrun.com/weblog/xhtmlvalidator-02-released/</link>
	<description>nutrun</description>
	<pubDate>Thu, 20 Nov 2008 11:20:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: George Malamidis</title>
		<link>http://nutrun.com/weblog/xhtmlvalidator-02-released/#comment-158</link>
		<dc:creator>George Malamidis</dc:creator>
		<pubDate>Wed, 06 Sep 2006 21:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=47#comment-158</guid>
		<description>XhtmlValidator will only do XHTML for a number of reasons:

Only the XHTML DTDs are included in the distribution. The library uses those to validate documents. Any other XML can be validated, provided the relevant DTD can be accessed.

javax.xml.parsers.DocumentBuilderFactory is used and is set to validating = true. This means that only well formed XML will get parsed, and HTML doesn't fall in this category.

It would only take a few really minor changes to accommodate HTML validation, but I would rather not put those in a release, because HTML is not well formed and it kind of beats the whole purpose of the library in my opinion.</description>
		<content:encoded><![CDATA[<p>XhtmlValidator will only do XHTML for a number of reasons:</p>
<p>Only the XHTML DTDs are included in the distribution. The library uses those to validate documents. Any other XML can be validated, provided the relevant DTD can be accessed.</p>
<p>javax.xml.parsers.DocumentBuilderFactory is used and is set to validating = true. This means that only well formed XML will get parsed, and HTML doesn&#8217;t fall in this category.</p>
<p>It would only take a few really minor changes to accommodate HTML validation, but I would rather not put those in a release, because HTML is not well formed and it kind of beats the whole purpose of the library in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Popescu</title>
		<link>http://nutrun.com/weblog/xhtmlvalidator-02-released/#comment-157</link>
		<dc:creator>Alex Popescu</dc:creator>
		<pubDate>Wed, 06 Sep 2006 20:52:47 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=47#comment-157</guid>
		<description>Hi!

Interesting work. I am wondering if the library is validating also HTML fragments or is it bound to work only with full XHTML?

./alex
--
.w( the_mindstorm )p.</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>Interesting work. I am wondering if the library is validating also HTML fragments or is it bound to work only with full XHTML?</p>
<p>./alex<br />
&#8211;<br />
.w( the_mindstorm )p.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahmed Hashim</title>
		<link>http://nutrun.com/weblog/xhtmlvalidator-02-released/#comment-156</link>
		<dc:creator>Ahmed Hashim</dc:creator>
		<pubDate>Thu, 31 Aug 2006 08:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=47#comment-156</guid>
		<description>Hi George,
Thank you for fixing the defect, actually your xhtml validator is simple and nice, it is doing the job using XML API's.

I am working now days in the Web standards and almost all my projects restrict to XHTML, so I am trying to make XHTML validation as unit testing which will reduce a lot of work and time, instead of validating the html in w3c validator site.

I tried the latest version from the validator 0.2 and I got another problem, if the page contain a fatal error, the validator will not continue validating the page and will stop. If the page contain errors or warning, it will work fine and return multiple errors. In my case, the fatal errors are important to figure out to fix it and should be reported to the developer to fix it, so I should have all errors in the page not only errors but also fatal errors.

How can I contribute to your projects?</description>
		<content:encoded><![CDATA[<p>Hi George,<br />
Thank you for fixing the defect, actually your xhtml validator is simple and nice, it is doing the job using XML API&#8217;s.</p>
<p>I am working now days in the Web standards and almost all my projects restrict to XHTML, so I am trying to make XHTML validation as unit testing which will reduce a lot of work and time, instead of validating the html in w3c validator site.</p>
<p>I tried the latest version from the validator 0.2 and I got another problem, if the page contain a fatal error, the validator will not continue validating the page and will stop. If the page contain errors or warning, it will work fine and return multiple errors. In my case, the fatal errors are important to figure out to fix it and should be reported to the developer to fix it, so I should have all errors in the page not only errors but also fatal errors.</p>
<p>How can I contribute to your projects?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
