<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Invalid HTML considered harmful</title>
	<atom:link href="http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/feed/" rel="self" type="application/rss+xml" />
	<link>http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/</link>
	<description>A blog, just like any blog, only more so</description>
	<lastBuildDate>Sat, 25 Jun 2011 15:45:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: This Blog Is Not For Reading &#187; Blog Archive &#187; Four things to improve your search result rankings</title>
		<link>http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/comment-page-1/#comment-8494</link>
		<dc:creator>This Blog Is Not For Reading &#187; Blog Archive &#187; Four things to improve your search result rankings</dc:creator>
		<pubDate>Sun, 26 Dec 2010 18:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/#comment-8494</guid>
		<description>[...] the page up high. That counts for all search engines, not just Google. I’ve written about this in Invalid HTML Considered Harmful. There are consultants that can help you correct invalid HTML; you may know one or two [...]</description>
		<content:encoded><![CDATA[<p>[...] the page up high. That counts for all search engines, not just Google. I’ve written about this in Invalid HTML Considered Harmful. There are consultants that can help you correct invalid HTML; you may know one or two [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: webdesign</title>
		<link>http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/comment-page-1/#comment-7637</link>
		<dc:creator>webdesign</dc:creator>
		<pubDate>Sun, 15 Aug 2010 10:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/#comment-7637</guid>
		<description>Thanks for the info. The topic This Blog Is Not For Reading  &#187; Blog Archive   &#187; Invalid HTML considered harmful was just what I was looking for. Will bookmark!</description>
		<content:encoded><![CDATA[<p>Thanks for the info. The topic This Blog Is Not For Reading  &raquo; Blog Archive   &raquo; Invalid HTML considered harmful was just what I was looking for. Will bookmark!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Paul Weber</title>
		<link>http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/comment-page-1/#comment-5325</link>
		<dc:creator>Stephen Paul Weber</dc:creator>
		<pubDate>Sun, 21 Mar 2010 16:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/#comment-5325</guid>
		<description>The bug is probably mostly in your theme.  I run WordPress at my site, and generate fully well-formed XHTML as well as mostly-valid XHTML5 (I output some legacy meta tags that HTML5 hates, I also use the rev=&quot;&quot; attribute which I do not believe should have been removed, and my use of ins and del tags is often just day-level granularity on datetime=&quot;&quot;)

Are you using the vanilla theme?  I could probably help you fix it up :)

About the inserting tel: links : do you have the WYSIWYG editor off completely, or are you using the &quot;code&quot; tab on it?  Turning it off is much safer.

I also use http://wordpress.org/extend/plugins/x-valid/ to make sure that commentors cannot insert markup that breaks my well-formedness.</description>
		<content:encoded><![CDATA[<p>The bug is probably mostly in your theme.  I run WordPress at my site, and generate fully well-formed XHTML as well as mostly-valid XHTML5 (I output some legacy meta tags that HTML5 hates, I also use the rev=&#8221;" attribute which I do not believe should have been removed, and my use of ins and del tags is often just day-level granularity on datetime=&#8221;")</p>
<p>Are you using the vanilla theme?  I could probably help you fix it up <img src='http://bob.jonkman.ca/blogs/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>About the inserting tel: links : do you have the WYSIWYG editor off completely, or are you using the &#8220;code&#8221; tab on it?  Turning it off is much safer.</p>
<p>I also use <a href="http://wordpress.org/extend/plugins/x-valid/" rel="nofollow">http://wordpress.org/extend/plugins/x-valid/</a> to make sure that commentors cannot insert markup that breaks my well-formedness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/comment-page-1/#comment-5317</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sun, 21 Mar 2010 02:34:09 +0000</pubDate>
		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/#comment-5317</guid>
		<description>I know it.  And I&#039;m not happy about it.

This is a Wordpress blog, which is oodles better than &lt;a href=&quot;http://thisblogisnotforreading.blogspot.com&quot; title=&quot;Blogspot: This Blog Is Not For Reading&quot; rel=&quot;nofollow&quot;&gt;the Blogspot blog I used to use&lt;/a&gt;. But, as you point out it&#039;s not perfect either.

I&#039;m not sure if the invalid HTML comes as a result of the templates or themes I&#039;m using, or if the Wordpress code itself is sloppy.  Certainly the editor is terrible.  I compose the posts with the non-WYSIWYG editor, but it won&#039;t let me insert certain types of markup.  For example, I tried to put in a URL with the tel: URI scheme, but the editor won&#039;t accept that.    &lt;a href=&quot;tel:+1-519-635-9413&quot;&gt; has the &quot;tel:&quot; stripped out.  Listen, Wordpress, &lt;em&gt;I&#039;m&lt;/em&gt; editing the code, and you should do what &lt;em&gt;I&lt;/em&gt; tell you to.

Sigh. Thanx for your sympathies.

--Bob.</description>
		<content:encoded><![CDATA[<p>I know it.  And I&#8217;m not happy about it.</p>
<p>This is a WordPress blog, which is oodles better than <a href="http://thisblogisnotforreading.blogspot.com" title="Blogspot: This Blog Is Not For Reading" rel="nofollow">the Blogspot blog I used to use</a>. But, as you point out it&#8217;s not perfect either.</p>
<p>I&#8217;m not sure if the invalid HTML comes as a result of the templates or themes I&#8217;m using, or if the WordPress code itself is sloppy.  Certainly the editor is terrible.  I compose the posts with the non-WYSIWYG editor, but it won&#8217;t let me insert certain types of markup.  For example, I tried to put in a URL with the tel: URI scheme, but the editor won&#8217;t accept that.    &lt;a href=&#8221;tel:+1-519-635-9413&#8243;&gt; has the &#8220;tel:&#8221; stripped out.  Listen, WordPress, <em>I&#8217;m</em> editing the code, and you should do what <em>I</em> tell you to.</p>
<p>Sigh. Thanx for your sympathies.</p>
<p>&#8211;Bob.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Paul Weber</title>
		<link>http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/comment-page-1/#comment-5316</link>
		<dc:creator>Stephen Paul Weber</dc:creator>
		<pubDate>Sun, 21 Mar 2010 01:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/2009/04/28/invalid-html-considered-harmful/#comment-5316</guid>
		<description>Ironically, this page does not validate.</description>
		<content:encoded><![CDATA[<p>Ironically, this page does not validate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

