<?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: Wordpress UTF-8 Charset Woes</title>
	<atom:link href="http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/</link>
	<description></description>
	<pubDate>Tue, 13 May 2008 05:35:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Wordpress UTF-8 Charset Problems &#171; The Official MartinZ Blog</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-75568</link>
		<dc:creator>Wordpress UTF-8 Charset Problems &#171; The Official MartinZ Blog</dc:creator>
		<pubDate>Tue, 16 Oct 2007 16:29:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-75568</guid>
		<description>[...] I realized it has got something to do with encoding UTF-8 charset, and found this useful article, Wordpress UTF-8 Charset Woes at MarteyDodoo.com. Will explore further and try solve the problem.     Posted by martinz Filed in [...]</description>
		<content:encoded><![CDATA[<p>[...] I realized it has got something to do with encoding UTF-8 charset, and found this useful article, Wordpress UTF-8 Charset Woes at MarteyDodoo.com. Will explore further and try solve the problem.     Posted by martinz Filed in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christophe</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-75103</link>
		<dc:creator>Christophe</dc:creator>
		<pubDate>Fri, 14 Sep 2007 08:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-75103</guid>
		<description>I found this post on the subject of UTF8 and version of WordPress below 2.2 to be useful:

&lt;a href="http://jonkenpon.com/2007/02/20/making-your-wordpress-database-portable-because-it-probably-isnt-right-now/" rel="nofollow"&gt;http://jonkenpon.com/2007/02/20/making-your-wordpress-database-portable-because-it-probably-isnt-right-now/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I found this post on the subject of UTF8 and version of WordPress below 2.2 to be useful:</p>
<p><a href="http://jonkenpon.com/2007/02/20/making-your-wordpress-database-portable-because-it-probably-isnt-right-now/" rel="nofollow" onclick="javascript:pageTracker._trackPageview ('/outbound/jonkenpon.com');">http://jonkenpon.com/2007/02/20/making-your-wordpress-database-portable-because-it-probably-isnt-right-now/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martey</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-74749</link>
		<dc:creator>Martey</dc:creator>
		<pubDate>Wed, 16 May 2007 05:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-74749</guid>
		<description>&lt;a href="http://trac.wordpress.org/ticket/3517" rel="nofollow"&gt;This issue&lt;/a&gt; is fixed in &lt;a href="http://wordpress.org/development/2007/05/wordpress-22/" rel="nofollow"&gt;WordPress 2.2&lt;/a&gt;, assuming you use the wp-config.php that comes with that version, which defines a 'DB_CHARSET' value that wp-db.php uses to run a SET NAMES query.</description>
		<content:encoded><![CDATA[<p><a href="http://trac.wordpress.org/ticket/3517" rel="nofollow" onclick="javascript:pageTracker._trackPageview ('/outbound/trac.wordpress.org');">This issue</a> is fixed in <a href="http://wordpress.org/development/2007/05/wordpress-22/" rel="nofollow" onclick="javascript:pageTracker._trackPageview ('/outbound/wordpress.org');">WordPress 2.2</a>, assuming you use the wp-config.php that comes with that version, which defines a &#039;DB_CHARSET&#039; value that wp-db.php uses to run a SET NAMES query.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oxborrow.net &#187; Blog Archive &#187; Wordpress migration and character encoding oddity</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-11002</link>
		<dc:creator>oxborrow.net &#187; Blog Archive &#187; Wordpress migration and character encoding oddity</dc:creator>
		<pubDate>Mon, 21 Aug 2006 00:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-11002</guid>
		<description>[...] It became quickly apparent I was not alone, as there are many topics regarding this problem and they all had a common &#8220;fix&#8221;, adding something similar to $this-&#62;query(&#8221;SET NAMES &#8216;utf8&#8242;&#8221;); into Wordpress&#8217;s main database include. This command tells MySQL to treat its connections as utf8 (or maybe it automatically converts them to utf8) Thinking back to the previous query I ran that showed the new server was handling all matters in utf8 I had little belief this would work, but tried it anyway as it seemed to solve so many other peoples cases. Sure enough this didn&#8217;t work for me. Not the blindest bit of difference. Since the two databases were handling the connections differently, out of curiosity I tried this command instead: $this-&#62;query(&#8221;SET NAMES &#8216;latin1&#8242;&#8221;); To my understanding this *shouldn&#8217;t* work&#8230; but it does. Anyway, everything is back to normal although I&#8217;m a little more confused than I was before. [...]</description>
		<content:encoded><![CDATA[<p>[...] It became quickly apparent I was not alone, as there are many topics regarding this problem and they all had a common &#034;fix&#034;, adding something similar to $this-&gt;query(&#034;SET NAMES &#039;utf8&#039;&#034;); into Wordpress&#039;s main database include. This command tells MySQL to treat its connections as utf8 (or maybe it automatically converts them to utf8) Thinking back to the previous query I ran that showed the new server was handling all matters in utf8 I had little belief this would work, but tried it anyway as it seemed to solve so many other peoples cases. Sure enough this didn&#039;t work for me. Not the blindest bit of difference. Since the two databases were handling the connections differently, out of curiosity I tried this command instead: $this-&gt;query(&#034;SET NAMES &#039;latin1&#039;&#034;); To my understanding this *shouldn&#039;t* work&#8230; but it does. Anyway, everything is back to normal although I&#039;m a little more confused than I was before. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Geeky Junkyard of kingler &#187; Blog Archive &#187; Upgraded to 2.0.1 (finally&#8230;)</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-4394</link>
		<dc:creator>The Geeky Junkyard of kingler &#187; Blog Archive &#187; Upgraded to 2.0.1 (finally&#8230;)</dc:creator>
		<pubDate>Tue, 21 Feb 2006 01:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-4394</guid>
		<description>[...] You may have noticed that it has been over a month since my last post. Oh, yeah, how time flies! My old web server died right before my grandma and mom came to visit me. So not until yesterday was I able to recover here. //sigh Moving to a new server turned out to be a big pain, just like moving to a new place in the real world. All the posts of my other WordPress blog with Chinese characters in UTF-8 encoding got messed up after the import. Considering the fact that the server was already dead, I almost panicked. Luckily, with the help of almighty google search, I found the following site complaining the same issue: Wordpress UTF-8 Charset Woes. I then added the suggested query (&#8221;SET NAMES &#8216;utf8&#8242;&#8221;) into the wp-db.php and it worked! [...]</description>
		<content:encoded><![CDATA[<p>[...] You may have noticed that it has been over a month since my last post. Oh, yeah, how time flies! My old web server died right before my grandma and mom came to visit me. So not until yesterday was I able to recover here. //sigh Moving to a new server turned out to be a big pain, just like moving to a new place in the real world. All the posts of my other WordPress blog with Chinese characters in UTF-8 encoding got messed up after the import. Considering the fact that the server was already dead, I almost panicked. Luckily, with the help of almighty google search, I found the following site complaining the same issue: Wordpress UTF-8 Charset Woes. I then added the suggested query (&#034;SET NAMES &#039;utf8&#039;&#034;) into the wp-db.php and it worked! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kingler的废物收集站 &#187; Blog Archive &#187; 升级到了WordPress 2.0.1</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-4330</link>
		<dc:creator>kingler的废物收集站 &#187; Blog Archive &#187; 升级到了WordPress 2.0.1</dc:creator>
		<pubDate>Sat, 18 Feb 2006 20:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-4330</guid>
		<description>[...] 这几天由于变动服务器，化了不少时间，主要是因为MySQL 4.0对于UTF8编码的处理问题，现在算是好了。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 这几天由于变动服务器，化了不少时间，主要是因为MySQL 4.0对于UTF8编码的处理问题，现在算是好了。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MarteyDodoo.com &#187; Upgrading to WordPress 2.0</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-3433</link>
		<dc:creator>MarteyDodoo.com &#187; Upgrading to WordPress 2.0</dc:creator>
		<pubDate>Tue, 27 Dec 2005 05:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-3433</guid>
		<description>[...] For some strange reason, WordPress would not let me upgrade until I disabled Brian&#39;s Threaded Comments. Once that was accomplished, I only had to patch wp-db.php again to get Unicode characters to display properly and edit my .htaccess to remove the changes that WordPress had made, which prevented me from accessing my RSS aggregator. [...]</description>
		<content:encoded><![CDATA[<p>[...] For some strange reason, WordPress would not let me upgrade until I disabled Brian&#39;s Threaded Comments. Once that was accomplished, I only had to patch wp-db.php again to get Unicode characters to display properly and edit my .htaccess to remove the changes that WordPress had made, which prevented me from accessing my RSS aggregator. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Le-Fay</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-3351</link>
		<dc:creator>Le-Fay</dc:creator>
		<pubDate>Fri, 23 Dec 2005 14:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-3351</guid>
		<description>Thanks a lot !
I had te same problem, and it did the trick for me.</description>
		<content:encoded><![CDATA[<p>Thanks a lot !<br />
I had te same problem, and it did the trick for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chandu</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-2035</link>
		<dc:creator>Chandu</dc:creator>
		<pubDate>Wed, 26 Oct 2005 09:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-2035</guid>
		<description>Thanks alot for the info...
I was facing the same problem.... glad to see someone who has solved it already...
I will try it today...</description>
		<content:encoded><![CDATA[<p>Thanks alot for the info&#8230;<br />
I was facing the same problem&#8230;. glad to see someone who has solved it already&#8230;<br />
I will try it today&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: d.f.h</title>
		<link>http://www.marteydodoo.com/2005/08/02/wordpress-utf-8-charset-woes/#comment-685</link>
		<dc:creator>d.f.h</dc:creator>
		<pubDate>Sat, 13 Aug 2005 08:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.marteydodoo.com/?p=488#comment-685</guid>
		<description>thx, that's very helpful to me, cause i've got the same problem.</description>
		<content:encoded><![CDATA[<p>thx, that&#039;s very helpful to me, cause i&#039;ve got the same problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
