<?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 Charset Encoding Problem After Upgrading to Version 2.2</title>
	<atom:link href="http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/</link>
	<description>Living Digitally and Electronically</description>
	<lastBuildDate>Sun, 08 Nov 2009 22:07:22 +0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Snigel.nu &#8211; Olle Linge &#187; WordPress updated to version 2.8</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-584154</link>
		<dc:creator>Snigel.nu &#8211; Olle Linge &#187; WordPress updated to version 2.8</dc:creator>
		<pubDate>Fri, 03 Jul 2009 21:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-584154</guid>
		<description>[...] Update: Chinese and Swedish alike should be displayed properly now. The problem arises when converting to new versions of WorpPress, but by changing a few parameters, it&#8217;s possible to let WordPress revert to the old way of handling charactersets. The solution to the problem can be found here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Update: Chinese and Swedish alike should be displayed properly now. The problem arises when converting to new versions of WorpPress, but by changing a few parameters, it&#8217;s possible to let WordPress revert to the old way of handling charactersets. The solution to the problem can be found here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: babysitter</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-573015</link>
		<dc:creator>babysitter</dc:creator>
		<pubDate>Sun, 03 May 2009 03:20:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-573015</guid>
		<description>I solved following these steps:
http://www.levysoft.it/archivio/2007/07/06/risolvere-il-problema-della-visualizzazione-errata-dei-caratteri-accentati-su-wordpress-cambiando-il-charset-da-iso-8859-a-utf-8/</description>
		<content:encoded><![CDATA[<p>I solved following these steps:<br />
<a href="http://www.levysoft.it/archivio/2007/07/06/risolvere-il-problema-della-visualizzazione-errata-dei-caratteri-accentati-su-wordpress-cambiando-il-charset-da-iso-8859-a-utf-8/" rel="nofollow">http://www.levysoft.it/archivio/2007/07/06/risolvere-il-problema-della-visualizzazione-errata-dei-caratteri-accentati-su-wordpress-cambiando-il-charset-da-iso-8859-a-utf-8/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RaiulBaztepo</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-568031</link>
		<dc:creator>RaiulBaztepo</dc:creator>
		<pubDate>Sat, 28 Mar 2009 21:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-568031</guid>
		<description>Hello!
Very Interesting post! Thank you for such interesting resource! 
PS: Sorry for my bad english, I&#039;v just started to learn this language ;)
See you! 
Your, Raiul Baztepo</description>
		<content:encoded><![CDATA[<p>Hello!<br />
Very Interesting post! Thank you for such interesting resource!<br />
PS: Sorry for my bad english, I&#8217;v just started to learn this language <img src='http://www.mydigitallife.info/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /><br />
See you!<br />
Your, Raiul Baztepo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marek</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-558394</link>
		<dc:creator>Marek</dc:creator>
		<pubDate>Fri, 30 Jan 2009 18:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-558394</guid>
		<description>Thank you a lot! It worked out perfectly. Now, I have to convert everything to UTF8.</description>
		<content:encoded><![CDATA[<p>Thank you a lot! It worked out perfectly. Now, I have to convert everything to UTF8.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: مشاكل الترميز Encoding في Wordpress 2.2 بعد الترقية &#124; سوالف حسن</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-549112</link>
		<dc:creator>مشاكل الترميز Encoding في Wordpress 2.2 بعد الترقية &#124; سوالف حسن</dc:creator>
		<pubDate>Tue, 23 Dec 2008 04:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-549112</guid>
		<description>[...] WordPress Charset Encoding Problem After Upgrading to Version 2.2 اقرأ المزيد عن ...أهلا 2.5، ومرة أخرى مشكلة الترميز بحمدالله تم الانتقال إلى النسخة الحديثة 2.5 من ووردبريس، وكل...ما الجديد! تم اصدار نسخة جديدة من برنامج ووردبريس، وكما ذكر في...WYSI-Wordpress محرر نصوص متقدم Wysi-Wordpress محرر تنسيق المدونات لمن يريد اختيارات أكثر و حرية... [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress Charset Encoding Problem After Upgrading to Version 2.2 اقرأ المزيد عن &#8230;أهلا 2.5، ومرة أخرى مشكلة الترميز بحمدالله تم الانتقال إلى النسخة الحديثة 2.5 من ووردبريس، وكل&#8230;ما الجديد! تم اصدار نسخة جديدة من برنامج ووردبريس، وكما ذكر في&#8230;WYSI-Wordpress محرر نصوص متقدم Wysi-Wordpress محرر تنسيق المدونات لمن يريد اختيارات أكثر و حرية&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommy</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-535936</link>
		<dc:creator>Tommy</dc:creator>
		<pubDate>Fri, 17 Oct 2008 05:15:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-535936</guid>
		<description>Thank you for this post!</description>
		<content:encoded><![CDATA[<p>Thank you for this post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fix odd characters in Wordpress posts &#124; Chris Fay &#38; Jennie Fay&#8217;s Webportal</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-531442</link>
		<dc:creator>Fix odd characters in Wordpress posts &#124; Chris Fay &#38; Jennie Fay&#8217;s Webportal</dc:creator>
		<pubDate>Tue, 16 Sep 2008 02:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-531442</guid>
		<description>[...] caused due to the encoding and collation, however after following the recommendations of sites like http://www.mydigitallife.info/2007/0&#8230;to-version-22/ I was still unable to get rid of the huge amount of garbled characters. Ultimately, I spent some [...]</description>
		<content:encoded><![CDATA[<p>[...] caused due to the encoding and collation, however after following the recommendations of sites like <a href="http://www.mydigitallife.info/2007/0&#8230;to-version-22/" rel="nofollow">http://www.mydigitallife.info/2007/0&#8230;to-version-22/</a> I was still unable to get rid of the huge amount of garbled characters. Ultimately, I spent some [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula G</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-530148</link>
		<dc:creator>Paula G</dc:creator>
		<pubDate>Sat, 06 Sep 2008 11:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-530148</guid>
		<description>Thanks so much -- you saved me hours of hair pulling!</description>
		<content:encoded><![CDATA[<p>Thanks so much &#8212; you saved me hours of hair pulling!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ates Goral</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-528779</link>
		<dc:creator>Ates Goral</dc:creator>
		<pubDate>Sun, 24 Aug 2008 03:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-528779</guid>
		<description>Thanks! Saved me a lot of time.</description>
		<content:encoded><![CDATA[<p>Thanks! Saved me a lot of time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodrigo</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-528687</link>
		<dc:creator>Rodrigo</dc:creator>
		<pubDate>Fri, 22 Aug 2008 21:24:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-528687</guid>
		<description>thanks</description>
		<content:encoded><![CDATA[<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Endolith</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-514871</link>
		<dc:creator>Endolith</dc:creator>
		<pubDate>Wed, 18 Jun 2008 00:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-514871</guid>
		<description>Isn&#039;t UTF8 much better?  Why would you limit yourself to Latin1 just because it used to be the default?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t UTF8 much better?  Why would you limit yourself to Latin1 just because it used to be the default?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Clarke</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-511596</link>
		<dc:creator>Tom Clarke</dc:creator>
		<pubDate>Fri, 06 Jun 2008 12:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-511596</guid>
		<description>Just wanted to say: this had afflicted me for months. Never found a workable solution. Stumbled on your site today and it worked perfectly. Thanks so much!</description>
		<content:encoded><![CDATA[<p>Just wanted to say: this had afflicted me for months. Never found a workable solution. Stumbled on your site today and it worked perfectly. Thanks so much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-466611</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Mon, 18 Feb 2008 21:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-466611</guid>
		<description>Hi, thanks for doing this. it&#039;s the only thing I&#039;ve found. I remove the utf8 and a lot of my posts still have the question marks. any ideas what I may need to do?</description>
		<content:encoded><![CDATA[<p>Hi, thanks for doing this. it&#8217;s the only thing I&#8217;ve found. I remove the utf8 and a lot of my posts still have the question marks. any ideas what I may need to do?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marthin</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-466267</link>
		<dc:creator>Marthin</dc:creator>
		<pubDate>Sat, 16 Feb 2008 19:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-466267</guid>
		<description>thanks for the help, it worked out for me :)</description>
		<content:encoded><![CDATA[<p>thanks for the help, it worked out for me <img src='http://www.mydigitallife.info/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruno Silva</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-2/#comment-457749</link>
		<dc:creator>Bruno Silva</dc:creator>
		<pubDate>Fri, 04 Jan 2008 22:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-457749</guid>
		<description>Thx a lot!
You saved me hours!</description>
		<content:encoded><![CDATA[<p>Thx a lot!<br />
You saved me hours!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Back on track! &#124; isa costa * the geek side</title>
		<link>http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/comment-page-1/#comment-408880</link>
		<dc:creator>Back on track! &#124; isa costa * the geek side</dc:creator>
		<pubDate>Sun, 18 Nov 2007 19:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/06/18/wordpress-charset-encoding-problem-after-upgrading-to-version-22/#comment-408880</guid>
		<description>[...] de upgrade (localizado em wp-admin/upgrade.php), os posts apareciam com os acentos todos marados. A solução mais rápida é editar o ficheiro wp-config.php e deixar os valores das constantes DB_CHARSET e [...]</description>
		<content:encoded><![CDATA[<p>[...] de upgrade (localizado em wp-admin/upgrade.php), os posts apareciam com os acentos todos marados. A solução mais rápida é editar o ficheiro wp-config.php e deixar os valores das constantes DB_CHARSET e [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
