<?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: Fix Wrong Encoding After Upgrade WordPress 2.2</title>
	<atom:link href="http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/</link>
	<description>Tech, Web, How to, Reviews, Tips, Downloads, and Make Money Online</description>
	<pubDate>Fri, 05 Dec 2008 02:49:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Halibutt</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-319757</link>
		<dc:creator>Halibutt</dc:creator>
		<pubDate>Mon, 25 Aug 2008 20:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-319757</guid>
		<description>Thanks, mate, you helped me a lot.</description>
		<content:encoded><![CDATA[<p>Thanks, mate, you helped me a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Craig</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-309714</link>
		<dc:creator>Daniel Craig</dc:creator>
		<pubDate>Wed, 23 Jul 2008 15:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-309714</guid>
		<description>Hi, I was looking around for a while searching for internet security solutions and I happened upon this site and your post regarding ng Encoding After Upgrade WordPress 2.2, I will definitely this to my internet security solutions bookmarks!</description>
		<content:encoded><![CDATA[<p>Hi, I was looking around for a while searching for internet security solutions and I happened upon this site and your post regarding ng Encoding After Upgrade WordPress 2.2, I will definitely this to my internet security solutions bookmarks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian&#8217;s blog &#187; Blog Archive &#187; Characters not showing up</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-305836</link>
		<dc:creator>Ian&#8217;s blog &#187; Blog Archive &#187; Characters not showing up</dc:creator>
		<pubDate>Thu, 08 May 2008 18:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-305836</guid>
		<description>[...] I needed to do this to make it [...]</description>
		<content:encoded><![CDATA[<p>[...] I needed to do this to make it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: su deposu</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-304095</link>
		<dc:creator>su deposu</dc:creator>
		<pubDate>Fri, 04 Apr 2008 20:54:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-304095</guid>
		<description>Will i do anything wrong if the visitor translates the page with say GOOGLE translate.</description>
		<content:encoded><![CDATA[<p>Will i do anything wrong if the visitor translates the page with say GOOGLE translate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: article good</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-303545</link>
		<dc:creator>article good</dc:creator>
		<pubDate>Sun, 23 Mar 2008 17:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-303545</guid>
		<description>Thanks...
That solved the problems.</description>
		<content:encoded><![CDATA[<p>Thanks&#8230;<br />
That solved the problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jiyan</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-300063</link>
		<dc:creator>Jiyan</dc:creator>
		<pubDate>Mon, 17 Dec 2007 21:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-300063</guid>
		<description>Thanks for helping me out.  I was worried I'd have to go through and manually edit all the f-d up articles!!!</description>
		<content:encoded><![CDATA[<p>Thanks for helping me out.  I was worried I&#8217;d have to go through and manually edit all the f-d up articles!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: senn</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-293583</link>
		<dc:creator>senn</dc:creator>
		<pubDate>Sat, 25 Aug 2007 10:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-293583</guid>
		<description>That solved the problems. Thanks!</description>
		<content:encoded><![CDATA[<p>That solved the problems. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LcF</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-293225</link>
		<dc:creator>LcF</dc:creator>
		<pubDate>Mon, 13 Aug 2007 17:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-293225</guid>
		<description>@Hrafn: glad that the simple solution helped you so much :)</description>
		<content:encoded><![CDATA[<p>@Hrafn: glad that the simple solution helped you so much <img src='http://www.liewcf.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hthth</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-293223</link>
		<dc:creator>hthth</dc:creator>
		<pubDate>Mon, 13 Aug 2007 16:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-293223</guid>
		<description>Thanks so much for discovering this solution and sharing it! I was staring down the barrel of manually correcting my posts, but thanks to you everything seems fine now. 

-Hrafn</description>
		<content:encoded><![CDATA[<p>Thanks so much for discovering this solution and sharing it! I was staring down the barrel of manually correcting my posts, but thanks to you everything seems fine now. </p>
<p>-Hrafn</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deb.foocode.net &#187; One Post to Cover Several</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-291281</link>
		<dc:creator>deb.foocode.net &#187; One Post to Cover Several</dc:creator>
		<pubDate>Sun, 24 Jun 2007 03:14:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-291281</guid>
		<description>[...] come up with a very simple set of instructions that work! Thanks LiewCF. You can either check out his post or follow his instructions (which I shall repeat) [...]</description>
		<content:encoded><![CDATA[<p>[...] come up with a very simple set of instructions that work! Thanks LiewCF. You can either check out his post or follow his instructions (which I shall repeat) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Getting Hebrew to work on WordPress 2.2 &#187; wordpressgarage.com</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290730</link>
		<dc:creator>Getting Hebrew to work on WordPress 2.2 &#187; wordpressgarage.com</dc:creator>
		<pubDate>Wed, 06 Jun 2007 08:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290730</guid>
		<description>[...] I found the solution! Liew Cheon Fong at LiewCF has nonchalantly posted a simple solution that works, as if it&#8217;s not the most brilliant thing ever! (Ok, I exaggerate, but [...]</description>
		<content:encoded><![CDATA[<p>[...] I found the solution! Liew Cheon Fong at LiewCF has nonchalantly posted a simple solution that works, as if it&#8217;s not the most brilliant thing ever! (Ok, I exaggerate, but [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: افكار و احلام &#187; WordPress 2.2 and the importance of doing Unicode right, from the start</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290563</link>
		<dc:creator>افكار و احلام &#187; WordPress 2.2 and the importance of doing Unicode right, from the start</dc:creator>
		<pubDate>Sat, 02 Jun 2007 06:29:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290563</guid>
		<description>[...] there seems to be a (fragile?) simple hack to “fix” the problem; the solution was Google’s first hit (now there’s technology working for you!) and the gibberish is banished. [...]</description>
		<content:encoded><![CDATA[<p>[...] there seems to be a (fragile?) simple hack to “fix” the problem; the solution was Google’s first hit (now there’s technology working for you!) and the gibberish is banished. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LcF</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290529</link>
		<dc:creator>LcF</dc:creator>
		<pubDate>Fri, 01 Jun 2007 06:21:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290529</guid>
		<description>@Pranjal: It should work because the page will use the default charset "utf8_general_ci" (unicode, Multilingual). The Google Translate *should* read the content.</description>
		<content:encoded><![CDATA[<p>@Pranjal: It should work because the page will use the default charset &#8220;utf8_general_ci&#8221; (unicode, Multilingual). The Google Translate *should* read the content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pranjal</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290526</link>
		<dc:creator>Pranjal</dc:creator>
		<pubDate>Fri, 01 Jun 2007 05:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290526</guid>
		<description>Will i do anything wrong if the visitor translates the page with say GOOGLE translate.</description>
		<content:encoded><![CDATA[<p>Will i do anything wrong if the visitor translates the page with say GOOGLE translate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Mycah</title>
		<link>http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290495</link>
		<dc:creator>Andrew Mycah</dc:creator>
		<pubDate>Thu, 31 May 2007 13:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.liewcf.com/blog/archives/2007/05/fix-wrong-encoding-after-upgrade-wordpress-22/#comment-290495</guid>
		<description>thanks for the tip!
simple and handy</description>
		<content:encoded><![CDATA[<p>thanks for the tip!<br />
simple and handy</p>
]]></content:encoded>
	</item>
</channel>
</rss>
