<?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>WordPress with multibyte languages へのコメント</title>
	<atom:link href="http://waviaei.com/2006/02/16/wordpress-with-multibyte-languages/feed/" rel="self" type="application/rss+xml" />
	<link>http://waviaei.com/2006/02/16/wordpress-with-multibyte-languages/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-with-multibyte-languages</link>
	<description>WordPress、写真・カメラ、本、Web関連やガジェットなどの話題を書いているブログです。</description>
	<lastBuildDate>Wed, 02 May 2012 16:46:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Toru より</title>
		<link>http://waviaei.com/2006/02/16/wordpress-with-multibyte-languages/#comment-3761</link>
		<dc:creator>Toru</dc:creator>
		<pubDate>Fri, 17 Feb 2006 10:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://waviaei.com/2006/02/16/wordpress-with-multibyte-languages/#comment-3761</guid>
		<description>So it is the same case in Korean too then. A Japanese version of WordPress is actuaaly called &quot;WordPressME&quot;. ME is for Multilingual Editon. From what I know, there are slight deffernces in the core file, maily for, as always, the language issue. Whereas its a one solution, the ideal solution for me is to &quot;sort out&quot; the porblem in the WordPress itself, rather than making ME version.
If there are anyone out there who are PHP programmer, and willing to give a hand to the WordPress dev. team, on using Asian languages, then that would be great. I think we, Japanese, tends to isolate ourselves in this kind of project...</description>
		<content:encoded><![CDATA[<p>So it is the same case in Korean too then. A Japanese version of WordPress is actuaaly called &#8220;WordPressME&#8221;. ME is for Multilingual Editon. From what I know, there are slight deffernces in the core file, maily for, as always, the language issue. Whereas its a one solution, the ideal solution for me is to &#8220;sort out&#8221; the porblem in the WordPress itself, rather than making ME version.<br />
If there are anyone out there who are PHP programmer, and willing to give a hand to the WordPress dev. team, on using Asian languages, then that would be great. I think we, Japanese, tends to isolate ourselves in this kind of project&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>oldlovas より</title>
		<link>http://waviaei.com/2006/02/16/wordpress-with-multibyte-languages/#comment-3760</link>
		<dc:creator>oldlovas</dc:creator>
		<pubDate>Thu, 16 Feb 2006 18:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://waviaei.com/2006/02/16/wordpress-with-multibyte-languages/#comment-3760</guid>
		<description>there are many problems with asian text. i think we have many problems as you guys. it&#039;s the same way of working problem with korean.

maybe we should make our own way of working.</description>
		<content:encoded><![CDATA[<p>there are many problems with asian text. i think we have many problems as you guys. it&#8217;s the same way of working problem with korean.</p>
<p>maybe we should make our own way of working.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

