<?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: Wait, so it&#8217;s the same word but&#8230; not? When does the madness end??</title>
	<atom:link href="http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/feed/" rel="self" type="application/rss+xml" />
	<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/</link>
	<description>Nihongo.3Yen.com - Japanese Language</description>
	<lastBuildDate>Fri, 18 Dec 2009 12:09:56 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: lenny</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-445</link>
		<dc:creator>lenny</dc:creator>
		<pubDate>Fri, 12 May 2006 15:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-445</guid>
		<description>Actually, ATOK does support Osaka-ben, as well as quite a few other dialects.

These are all examples of 異字同訓. They can be a pain in the ass, but are useful once you figure out the differences. 収まる・治まる・修まる・修まる 
If you study for the Kanji Kentei you will be forced to learn the difference. There is actually an official chart called the 「異字同訓」の漢字の用法 (produced in 1973) illustrating when to use which Kanji, or even just to write in kana.</description>
		<content:encoded><![CDATA[<p>Actually, ATOK does support Osaka-ben, as well as quite a few other dialects.</p>
<p>These are all examples of 異字同訓. They can be a pain in the ass, but are useful once you figure out the differences. 収まる・治まる・修まる・修まる<br />
If you study for the Kanji Kentei you will be forced to learn the difference. There is actually an official chart called the 「異字同訓」の漢字の用法 (produced in 1973) illustrating when to use which Kanji, or even just to write in kana.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-438</link>
		<dc:creator>Colin</dc:creator>
		<pubDate>Wed, 10 May 2006 07:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-438</guid>
		<description>Thanks for that post. Kanji is a powerful tool when you start to learn this type of thing. Another example I am familar with is 斬る which is to cut someone with a sword. This also means we need to be careful not to press the spacebar too many times when typing a word.</description>
		<content:encoded><![CDATA[<p>Thanks for that post. Kanji is a powerful tool when you start to learn this type of thing. Another example I am familar with is 斬る which is to cut someone with a sword. This also means we need to be careful not to press the spacebar too many times when typing a word.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tae Kim</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-437</link>
		<dc:creator>Tae Kim</dc:creator>
		<pubDate>Wed, 10 May 2006 00:32:27 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-437</guid>
		<description>I tried resaving the post in UTF-8. If that doesn&#039;t work, I have no idea.</description>
		<content:encoded><![CDATA[<p>I tried resaving the post in UTF-8. If that doesn&#8217;t work, I have no idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angela I.</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-436</link>
		<dc:creator>Angela I.</dc:creator>
		<pubDate>Tue, 09 May 2006 18:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-436</guid>
		<description>Haha, this was probably one of the first things I noticed wheen starting to read kanji. But now, I&#039;ve gotten used to all the madness of what the kanji does.</description>
		<content:encoded><![CDATA[<p>Haha, this was probably one of the first things I noticed wheen starting to read kanji. But now, I&#8217;ve gotten used to all the madness of what the kanji does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shadowsong</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-435</link>
		<dc:creator>shadowsong</dc:creator>
		<pubDate>Tue, 09 May 2006 16:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-435</guid>
		<description>I syndicated your rss feed to livejournal as &lt;a href=&quot;http://syndicated.livejournal.com/tae_kim/&quot; rel=&quot;nofollow&quot;&gt;tae_kim&lt;/a&gt;.  However, I&#039;m having some encoding issues.

The default page encoding is UTF-8 both on my home computer and on my work computer. At home, the Japanese characters all show up as western letters with diacritics. Shift-JIS encoding gives me what looks like non-simplified Chinese  characters to my untrained eye - they&#039;re not the correct characters, at the very least.

At work, all but your most recent post display correctly in UTF-8, but the most recent post displays the same incorrect way as they all do at home, with diacritic vowels. &lt;a href=&quot;http://syndicated.livejournal.com/tae_kim/2622.html&quot; rel=&quot;nofollow&quot;&gt;Here&lt;/a&gt;&#039;s Livejournal&#039;s copy of the post that&#039;s not working for me.

Any idea what&#039;s going on?</description>
		<content:encoded><![CDATA[<p>I syndicated your rss feed to livejournal as <a href="http://syndicated.livejournal.com/tae_kim/" rel="nofollow">tae_kim</a>.  However, I&#8217;m having some encoding issues.</p>
<p>The default page encoding is UTF-8 both on my home computer and on my work computer. At home, the Japanese characters all show up as western letters with diacritics. Shift-JIS encoding gives me what looks like non-simplified Chinese  characters to my untrained eye &#8211; they&#8217;re not the correct characters, at the very least.</p>
<p>At work, all but your most recent post display correctly in UTF-8, but the most recent post displays the same incorrect way as they all do at home, with diacritic vowels. <a href="http://syndicated.livejournal.com/tae_kim/2622.html" rel="nofollow">Here</a>&#8217;s Livejournal&#8217;s copy of the post that&#8217;s not working for me.</p>
<p>Any idea what&#8217;s going on?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tae Kim</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-434</link>
		<dc:creator>Tae Kim</dc:creator>
		<pubDate>Tue, 09 May 2006 00:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-434</guid>
		<description>By &quot;not suck&quot;, I was thinking more along the lines of &quot;free&quot;, &quot;easy to use&quot; and &quot;doesn&#039;t crash&quot;. If it had support for Osaka-ben, I would upgrade that to pretty neat.

I heard atok was pretty good but somehow I just can&#039;t convince myself that it&#039;s worth paying $50-$60 dollars.

Of course, there&#039;s also 留まる and 停まる too.</description>
		<content:encoded><![CDATA[<p>By &#8220;not suck&#8221;, I was thinking more along the lines of &#8220;free&#8221;, &#8220;easy to use&#8221; and &#8220;doesn&#8217;t crash&#8221;. If it had support for Osaka-ben, I would upgrade that to pretty neat.</p>
<p>I heard atok was pretty good but somehow I just can&#8217;t convince myself that it&#8217;s worth paying $50-$60 dollars.</p>
<p>Of course, there&#8217;s also 留まる and 停まる too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: raize</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-433</link>
		<dc:creator>raize</dc:creator>
		<pubDate>Mon, 08 May 2006 15:14:20 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-433</guid>
		<description>I&#039;d just like to comment on the &quot;ime - only MSsoftware that doesn&#039;t suck.&quot; thing.  It actually kind of does, but no more or less than most.  I recently had a chance to check out ATOK 2006, and it pretty much kicked ass.  Google it up and check it out.  And for kicks, see if you can type 聯絡 (れんらく) on your ime. 

If you like, figure out the difference between it and 連絡.

Ooo, and how about 止まる and 泊まる?

Fun times.</description>
		<content:encoded><![CDATA[<p>I&#8217;d just like to comment on the &#8220;ime &#8211; only MSsoftware that doesn&#8217;t suck.&#8221; thing.  It actually kind of does, but no more or less than most.  I recently had a chance to check out ATOK 2006, and it pretty much kicked ass.  Google it up and check it out.  And for kicks, see if you can type 聯絡 (れんらく) on your ime. </p>
<p>If you like, figure out the difference between it and 連絡.</p>
<p>Ooo, and how about 止まる and 泊まる?</p>
<p>Fun times.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul D</title>
		<link>http://nihongo.3yen.com/2006-05-08/distinguishing-between-same-kanji/comment-page-1/#comment-432</link>
		<dc:creator>Paul D</dc:creator>
		<pubDate>Mon, 08 May 2006 13:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://nihongo.3yen.com/2006-02-01/distinguishing-between-same-kanji/#comment-432</guid>
		<description>I always get a kick out of how written Japanese imparts more information than the spoken language, and maybe even more than a typical passage in a Western language. Cool article!</description>
		<content:encoded><![CDATA[<p>I always get a kick out of how written Japanese imparts more information than the spoken language, and maybe even more than a typical passage in a Western language. Cool article!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
