<?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: WordPress formatting bugs</title>
	<atom:link href="http://coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/</link>
	<description>pro-gram-mer: n. a person who converts coffee into code</description>
	<pubDate>Wed, 07 Jan 2009 21:01:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: seks</title>
		<link>http://coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/comment-page-1/#comment-65871</link>
		<dc:creator>seks</dc:creator>
		<pubDate>Sun, 03 Dec 2006 08:33:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/#comment-65871</guid>
		<description>sport en weer</description>
		<content:encoded><![CDATA[<p>sport en weer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/comment-page-1/#comment-326</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Tue, 14 Dec 2004 16:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/#comment-326</guid>
		<description>I believe the auto-paragraphing code (wpautop) has been updated in 1.3 to fix some of its buginess.  And in a post later than this one I provided a more in-depth &lt;a href="http://www.coffee2code.com/archives/2004/08/02/examining-balancetags/"&gt;analysis of formatting problems&lt;/a&gt;, mainly related to WP's automatic tag balancer.  I also posted a &lt;a href="http://www.coffee2code.com/archives/2004/08/03/fixing-balancetags/"&gt;patch to fix the bugs&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I believe the auto-paragraphing code (wpautop) has been updated in 1.3 to fix some of its buginess.  And in a post later than this one I provided a more in-depth <a href="http://www.coffee2code.com/archives/2004/08/02/examining-balancetags/">analysis of formatting problems</a>, mainly related to WP&#8217;s automatic tag balancer.  I also posted a <a href="http://www.coffee2code.com/archives/2004/08/03/fixing-balancetags/">patch to fix the bugs</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Villines</title>
		<link>http://coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/comment-page-1/#comment-325</link>
		<dc:creator>Ken Villines</dc:creator>
		<pubDate>Tue, 14 Dec 2004 15:31:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/#comment-325</guid>
		<description>I guess using back ticks doesn't show the code?? sorry about that.</description>
		<content:encoded><![CDATA[<p>I guess using back ticks doesn&#8217;t show the code?? sorry about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Villines</title>
		<link>http://coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/comment-page-1/#comment-324</link>
		<dc:creator>Ken Villines</dc:creator>
		<pubDate>Tue, 14 Dec 2004 15:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffee2code.com/archives/2004/06/29/wordpress-formatting-bugs/#comment-324</guid>
		<description>I came across some issues too. It looks like having &lt;code&gt;&lt;p&gt; &lt;/P&gt;&lt;/code&gt; tags with &lt;code&gt;&lt;br&gt;&lt;/code&gt; tags imbedded within them breaks WP parsing. All &lt;code&gt;&lt;b&gt;&lt;/code&gt; tags have to be compliant like this &lt;code&gt;&lt;b /&gt;&lt;/code&gt;. I agree that WP should auto correct the stuff instead of having data loss like in my case.

I always run into the non-tag &lt;code&gt;&lt;/&gt;&lt;/code&gt;. I do run into it more when using the &lt;code&gt;&lt; !--more--&gt;&lt;/code&gt; tag 

-Ken</description>
		<content:encoded><![CDATA[<p>I came across some issues too. It looks like having <code>&lt;p&gt; &lt;/P&gt;</code> tags with <code>&lt;br&gt;</code> tags imbedded within them breaks WP parsing. All <code>&lt;b&gt;</code> tags have to be compliant like this <code>&lt;b /&gt;</code>. I agree that WP should auto correct the stuff instead of having data loss like in my case.</p>
<p>I always run into the non-tag <code>&lt;/&gt;</code>. I do run into it more when using the <code>&lt; !--more--&gt;</code> tag </p>
<p>-Ken</p>
]]></content:encoded>
	</item>
</channel>
</rss>
