<?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: 2.6 Release Candidate 2</title>
	<atom:link href="http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/</link>
	<description>An elegant, flexible WordPress theme</description>
	<lastBuildDate>Thu, 03 May 2012 14:34:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Abdullah ARIK</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6984</link>
		<dc:creator>Abdullah ARIK</dc:creator>
		<pubDate>Sun, 10 Jan 2010 09:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6984</guid>
		<description>Hi,

You can find Tarski 2.6 Turkish Language Files here: http://abdullaharik.com/tarski-temasi-turkce-dil-dosyasi/</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>You can find Tarski 2.6 Turkish Language Files here: <a href="http://abdullaharik.com/tarski-temasi-turkce-dil-dosyasi/" rel="nofollow">http://abdullaharik.com/tarski-temasi-turkce-dil-dosyasi/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Eastaugh</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6958</link>
		<dc:creator>Ben Eastaugh</dc:creator>
		<pubDate>Mon, 04 Jan 2010 15:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6958</guid>
		<description>Those elements aren&#039;t widely supported yet, and adding them in a way that&#039;s compatible with older browsers (particularly Internet Explorer) would take more work than I have time for right now (patches to improve the markup are welcome). This will be an incremental process; Tarski contains several thousand lines of code, and big changes don&#039;t happen overnight.

To nitpick slightly, the code isn&#039;t &quot;still XHTML&quot; (although I do understand what you&#039;re getting at)—it&#039;s valid HTML5, albeit not as semantic as I would like. My &lt;a href=&quot;http://extralogical.net/&quot; rel=&quot;nofollow&quot;&gt;personal site&lt;/a&gt; is a better demonstration of where this is going.</description>
		<content:encoded><![CDATA[<p>Those elements aren&#8217;t widely supported yet, and adding them in a way that&#8217;s compatible with older browsers (particularly Internet Explorer) would take more work than I have time for right now (patches to improve the markup are welcome). This will be an incremental process; Tarski contains several thousand lines of code, and big changes don&#8217;t happen overnight.</p>
<p>To nitpick slightly, the code isn&#8217;t &#8220;still XHTML&#8221; (although I do understand what you&#8217;re getting at)—it&#8217;s valid HTML5, albeit not as semantic as I would like. My <a href="http://extralogical.net/" rel="nofollow">personal site</a> is a better demonstration of where this is going.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6957</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Mon, 04 Jan 2010 15:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6957</guid>
		<description>Here&#039;s what I mean, and again I&#039;m just looking at the source for this page.

You are not using the following HTML 5 tags: header, hgroup, section, article, time, address, nav, aside, figure, footer.

There are a few themes out there that do use the tags I just mentioned in conjunction with the DOCTYPE. I&#039;m curious why, when to my eyes all of the layout and structure code is still XHTML, you would switch to HTML 5.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s what I mean, and again I&#8217;m just looking at the source for this page.</p>
<p>You are not using the following HTML 5 tags: header, hgroup, section, article, time, address, nav, aside, figure, footer.</p>
<p>There are a few themes out there that do use the tags I just mentioned in conjunction with the DOCTYPE. I&#8217;m curious why, when to my eyes all of the layout and structure code is still XHTML, you would switch to HTML 5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Eastaugh</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6954</link>
		<dc:creator>Ben Eastaugh</dc:creator>
		<pubDate>Mon, 04 Jan 2010 09:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6954</guid>
		<description>I&#039;ll try to sneak that one in too. Cheers Andreas.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll try to sneak that one in too. Cheers Andreas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Eastaugh</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6953</link>
		<dc:creator>Ben Eastaugh</dc:creator>
		<pubDate>Mon, 04 Jan 2010 09:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6953</guid>
		<description>All the markup generated by Tarski has changed; the markup generated directly by WordPress hasn&#039;t. Fortunately, HTML5 is broadly compatible with XHTML-style markup, self-closing tags and so on.

I made the &lt;code&gt;DOCTYPE&lt;/code&gt; change in order to support new HTML5 features, in compatible browsers. There aren&#039;t too many at the moment, but I anticipate more in the future. It seems fairly likely that WordPress core will make the change at some point in the not-too-distant-future.</description>
		<content:encoded><![CDATA[<p>All the markup generated by Tarski has changed; the markup generated directly by WordPress hasn&#8217;t. Fortunately, HTML5 is broadly compatible with XHTML-style markup, self-closing tags and so on.</p>
<p>I made the <code>DOCTYPE</code> change in order to support new HTML5 features, in compatible browsers. There aren&#8217;t too many at the moment, but I anticipate more in the future. It seems fairly likely that WordPress core will make the change at some point in the not-too-distant-future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6947</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Fri, 01 Jan 2010 10:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6947</guid>
		<description>Oh, and Happy New Year, by the way.</description>
		<content:encoded><![CDATA[<p>Oh, and Happy New Year, by the way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6943</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Thu, 31 Dec 2009 16:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6943</guid>
		<description>Please, don&#039;t forget to address the wp-caption issue in the upcoming release.</description>
		<content:encoded><![CDATA[<p>Please, don&#8217;t forget to address the wp-caption issue in the upcoming release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6942</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Thu, 31 Dec 2009 15:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6942</guid>
		<description>You&#039;re switching the doctype, but not any of the markup? I&#039;m looking at the source for this site and it is still using XHTML. So why switch the doctype without changing the markup?</description>
		<content:encoded><![CDATA[<p>You&#8217;re switching the doctype, but not any of the markup? I&#8217;m looking at the source for this site and it is still using XHTML. So why switch the doctype without changing the markup?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hellohunter</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6923</link>
		<dc:creator>hellohunter</dc:creator>
		<pubDate>Mon, 28 Dec 2009 18:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6923</guid>
		<description>Hi, I just wanted to say thanks for inventing Tarski. It&#039;s like, my favorite theme! It&#039;s real fresh and clean, and it fits my blog really well. Thanks again!!</description>
		<content:encoded><![CDATA[<p>Hi, I just wanted to say thanks for inventing Tarski. It&#8217;s like, my favorite theme! It&#8217;s real fresh and clean, and it fits my blog really well. Thanks again!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Eastaugh</title>
		<link>http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/comment-page-1/#comment-6921</link>
		<dc:creator>Ben Eastaugh</dc:creator>
		<pubDate>Sat, 26 Dec 2009 18:53:57 +0000</pubDate>
		<guid isPermaLink="false">http://tarskitheme.com/2009/12/21/2-6-release-candidate-1/#comment-6921</guid>
		<description>I haven&#039;t fixed it yet. There were some fairly serious changes in this version, so I want to give the bugs a chance to surface. My plan is to do another round of bug fixes before releasing 2.6, so I&#039;ll address this then.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t fixed it yet. There were some fairly serious changes in this version, so I want to give the bugs a chance to surface. My plan is to do another round of bug fixes before releasing 2.6, so I&#8217;ll address this then.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

