<?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: Movable Type, MySQL, Perl, Unicode</title>
	<atom:link href="http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/</link>
	<description>The art of keeping up with yesterday&#039;s blogging</description>
	<lastBuildDate>Fri, 19 Mar 2010 17:12:02 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: S Anand</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11059</link>
		<dc:creator>S Anand</dc:creator>
		<pubDate>Tue, 06 Mar 2007 18:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11059</guid>
		<description>&lt;p&gt;Thanks! I managed to get my comments system to work with &lt;span class=&quot;caps&quot;&gt;UTF8 &lt;/span&gt;through this post.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks! I managed to get my comments system to work with <span class="caps">UTF8 </span>through this post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Procrastination</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11066</link>
		<dc:creator>Procrastination</dc:creator>
		<pubDate>Tue, 28 Nov 2006 18:13:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11066</guid>
		<description>&lt;strong&gt;Movable Type and Unicode&lt;/strong&gt;

Running Movable Type natively in Unicode was not as difficult as I thought but it still required a number of patches to the code.
</description>
		<content:encoded><![CDATA[<p><strong>Movable Type and Unicode</strong></p>
<p>Running Movable Type natively in Unicode was not as difficult as I thought but it still required a number of patches to the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog @ eruhkim.net</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11065</link>
		<dc:creator>Blog @ eruhkim.net</dc:creator>
		<pubDate>Sat, 19 Aug 2006 15:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11065</guid>
		<description>&lt;strong&gt;MySQL 4.1과 MovableType의 궁합 문제&lt;/strong&gt;

왜인지 모르겠지만, MySQL 4.1로 바뀐 이후 접속을 할 때의 세션의 캐릭터셋이 utf8로 설정이 안 되는 것 같다. 그것때문에 고민하다가 MovableType의 경우 이러한 해결 방법을 찾아서 일단 해결. 좀더 근본적인 해결책을 찾는 중이다.......
</description>
		<content:encoded><![CDATA[<p><strong>MySQL 4.1과 MovableType의 궁합 문제</strong></p>
<p>왜인지 모르겠지만, MySQL 4.1로 바뀐 이후 접속을 할 때의 세션의 캐릭터셋이 utf8로 설정이 안 되는 것 같다. 그것때문에 고민하다가 MovableType의 경우 이러한 해결 방법을 찾아서 일단 해결. 좀더 근본적인 해결책을 찾는 중이다&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yuanwei's Living Room for his mind</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11064</link>
		<dc:creator>Yuanwei's Living Room for his mind</dc:creator>
		<pubDate>Tue, 04 Apr 2006 14:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11064</guid>
		<description>&lt;strong&gt;Movable Type Unicode Issue&lt;/strong&gt;

I have used MySQL as MobableType backend database. After I setup a Chinese blog, I suddenly found the double-byte characters stored in database table were bad encoded. But MT shows correct double-byte encode in the webpage. Even current MySQL and...
</description>
		<content:encoded><![CDATA[<p><strong>Movable Type Unicode Issue</strong></p>
<p>I have used MySQL as MobableType backend database. After I setup a Chinese blog, I suddenly found the double-byte characters stored in database table were bad encoded. But MT shows correct double-byte encode in the webpage. Even current MySQL and&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lucifer</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11058</link>
		<dc:creator>lucifer</dc:creator>
		<pubDate>Thu, 23 Feb 2006 14:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11058</guid>
		<description>&lt;p&gt;hwo’s perfect?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>hwo’s perfect?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 双生 &#124; iSdq.com</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11063</link>
		<dc:creator>双生 &#124; iSdq.com</dc:creator>
		<pubDate>Mon, 06 Feb 2006 14:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11063</guid>
		<description>&lt;strong&gt;WordPress和MovableType的MySQL乱码问题解决方法&lt;/strong&gt;

WordPress和MovableType是主流的Blog系统，而他们都用的是MySQL数据库，那么在MySQL4.1下，中文的WP和MT就会产生种种的乱码问题。 如前MySQL4.1乱码问题分析的，一个程序（ PHP，CGI 等）与MySQL建立连接后，这个程序发送给MySQL的数据采用的是什么字符集，MySQL 是无从得知的。所以解决乱码问题的根本就是我们在程序中告诉MySQL采用的编码是什么，简单的就是在程序中加入这样的一个语句： SET NAMES &#039;utf8&#039;。 这个语句的效果等同于同时设定了 SET character_set_client=&#039;utf8&#039;SET character_set_connection=&#039;utf8&#039;SET character_set_results=&#039;utf8&#039; 为什么这么做？ 我们安装MySQL4.1时按照默认配置，那么default-character-set= utf8。在MySQL Command Line Client下查看到的查看系统的字符集和排序方式的设定为： mysql&gt; SHOW VARIABLES LIKE &#039;character_set_%&#039;;+--------------------------+----------------------------+&#124; Variable_name&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &#124;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Value&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &#124;+--------------------------+----------------------------+&#124; character_set_client&#160;&#160;&#160;&#160; &#124; latin1&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &#124;&#124; character_set_connection &#124; latin1&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &#124;&#124; character_set_database&#160;&#160; &#124; utf8&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &#124;&#124;...
</description>
		<content:encoded><![CDATA[<p><strong>WordPress和MovableType的MySQL乱码问题解决方法</strong></p>
<p>WordPress和MovableType是主流的Blog系统，而他们都用的是MySQL数据库，那么在MySQL4.1下，中文的WP和MT就会产生种种的乱码问题。 如前MySQL4.1乱码问题分析的，一个程序（ PHP，CGI 等）与MySQL建立连接后，这个程序发送给MySQL的数据采用的是什么字符集，MySQL 是无从得知的。所以解决乱码问题的根本就是我们在程序中告诉MySQL采用的编码是什么，简单的就是在程序中加入这样的一个语句： SET NAMES &#8216;utf8&#8242;。 这个语句的效果等同于同时设定了 SET character_set_client=&#8217;utf8&#8242;SET character_set_connection=&#8217;utf8&#8242;SET character_set_results=&#8217;utf8&#8242; 为什么这么做？ 我们安装MySQL4.1时按照默认配置，那么default-character-set= utf8。在MySQL Command Line Client下查看到的查看系统的字符集和排序方式的设定为： mysql&gt; SHOW VARIABLES LIKE &#8216;character_set_%&#8217;;+&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;+&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-+| Variable_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |+&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;+&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-+| character_set_client&nbsp;&nbsp;&nbsp;&nbsp; | latin1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; || character_set_connection | latin1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; || character_set_database&nbsp;&nbsp; | utf8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ||&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11057</link>
		<dc:creator>Zack</dc:creator>
		<pubDate>Thu, 08 Dec 2005 16:52:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11057</guid>
		<description>&lt;p&gt;Eric: The Perl &lt;span class=&quot;caps&quot;&gt;DBD &lt;/span&gt;driver for postgresql has some, though not good, Unicode support. And I hope you know that there is &lt;a href=&quot;http://www.phpwact.org/php/i18n/charsets&quot; rel=&quot;nofollow&quot;&gt;no Unicode support in &lt;span class=&quot;caps&quot;&gt;PHP&lt;/span&gt;&lt;/a&gt; without mbstring extension.&lt;/p&gt;
&lt;p&gt;Scott: That is my current semi-solution as well. However, that still doesn’t mark the data as Unicode, though it does get copied from the database correctly.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Eric: The Perl <span class="caps">DBD </span>driver for postgresql has some, though not good, Unicode support. And I hope you know that there is <a href="http://www.phpwact.org/php/i18n/charsets" rel="nofollow">no Unicode support in <span class="caps">PHP</span></a> without mbstring extension.</p>
<p>Scott: That is my current semi-solution as well. However, that still doesn’t mark the data as Unicode, though it does get copied from the database correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Swanson</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11056</link>
		<dc:creator>Scott Swanson</dc:creator>
		<pubDate>Mon, 05 Dec 2005 13:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11056</guid>
		<description>&lt;p&gt;Just to let you know, I’ve been fighting with the database issue for a long time, and my standing workaround is to forcibly &lt;code&gt;SET NAMES &#039;utf8&#039;&lt;/code&gt; on every database connection &lt;em&gt;inside of MT&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://blog.truegeek.org/2004/12/07/22.56.24/&quot; rel=&quot;nofollow&quot;&gt;http://blog.truegeek.org/2004/12/07/22.56.24/&lt;/a&gt; for details.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Just to let you know, I’ve been fighting with the database issue for a long time, and my standing workaround is to forcibly <code>SET NAMES 'utf8'</code> on every database connection <em>inside of MT</em>.</p>
<p><a href="http://blog.truegeek.org/2004/12/07/22.56.24/" rel="nofollow">http://blog.truegeek.org/2004/12/07/22.56.24/</a> for details.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: julik live</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11062</link>
		<dc:creator>julik live</dc:creator>
		<pubDate>Fri, 02 Dec 2005 23:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11062</guid>
		<description>&lt;strong&gt;Интересно, через сколько лет&lt;/strong&gt;

&#8230;эти люди вырастут и научатся делать это а) сами б) сразу Причем это паттерн. The floggings will continue until morale improves With ruby, though, it isn’t just a case of American programmers forgetting to think about the other 95% of......
</description>
		<content:encoded><![CDATA[<p><strong>Интересно, через сколько лет</strong></p>
<p>&#8230;эти люди вырастут и научатся делать это а) сами б) сразу Причем это паттерн. The floggings will continue until morale improves With ruby, though, it isn’t just a case of American programmers forgetting to think about the other 95% of&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: julik live</title>
		<link>http://www.zackvision.com/weblog/2005/11/mt-unicode-mysql/comment-page-1/#comment-11061</link>
		<dc:creator>julik live</dc:creator>
		<pubDate>Tue, 29 Nov 2005 23:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackvision.com/?p=1387#comment-11061</guid>
		<description>&lt;strong&gt;Интересно, через сколько лет&lt;/strong&gt;

&#8230;эти люди вырастут и научатся делать это а) сами б) сразу Причем это паттерн. The floggings will continue until morale improves With ruby, though, it isn’t just a case of American programmers forgetting to think about the other 95% of......
</description>
		<content:encoded><![CDATA[<p><strong>Интересно, через сколько лет</strong></p>
<p>&#8230;эти люди вырастут и научатся делать это а) сами б) сразу Причем это паттерн. The floggings will continue until morale improves With ruby, though, it isn’t just a case of American programmers forgetting to think about the other 95% of&#8230;&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
