<?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: Jim Breen on the iPhone</title>
	<atom:link href="http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/</link>
	<description>A Japanese Language &#38; Culture Blog</description>
	<lastBuildDate>Sun, 13 Apr 2014 12:48:14 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.8.2</generator>
	<item>
		<title>By: Peter</title>
		<link>http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/comment-page-2/#comment-18166</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Fri, 09 Apr 2010 12:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.tofugu.com/?p=564#comment-18166</guid>
		<description><![CDATA[I&#039;m kind of put off that iJisho claims you can use the Chinese handwriting input to enter kanji without mentioning that it doesn&#039;t work very well for a lot of kanji, and it doesn&#039;t work at all for many others, even some very common ones.   If you buy the app expecting to be able to enter kanji by handwriting, you&#039;re going to be frustrated.  Simply put, Chinese hanzi and Japanese kanji have been evolving separately for 1300+ years, so the characters aren&#039;t all the same anymore.  Some kanji, even common ones, don&#039;t exist in Chinese, and others have a different stroke order (confounding the handwriting system if you enter the correct Japanese stroke order).   It&#039;s a good thing to use, but you can&#039;t depend on it for finding kanji, because a frustratingly high percentage of the time, it just won&#039;t work.&lt;br&gt;&lt;br&gt;For some of the common kanji that aren&#039;t in Chinese and more detail on why they&#039;re not, see &lt;a href=&quot;http://en.wikipedia.org/wiki/Chinese_character#Comparisons_of_Traditional.2C_Simplified_and_Kanji&quot; rel=&quot;nofollow&quot;&gt;http://en.wikipedia.org/wiki/Chinese_character#...&lt;/a&gt; &lt;br&gt;&lt;br&gt;Try entering the kanji for, e.g., common kanji like the ones for black, Buddha, and the &quot;ki&quot; in &quot;genki&quot; (and thousands of other words) on your iPhone.]]></description>
		<content:encoded><![CDATA[<p>I&#39;m kind of put off that iJisho claims you can use the Chinese handwriting input to enter kanji without mentioning that it doesn&#39;t work very well for a lot of kanji, and it doesn&#39;t work at all for many others, even some very common ones.   If you buy the app expecting to be able to enter kanji by handwriting, you&#39;re going to be frustrated.  Simply put, Chinese hanzi and Japanese kanji have been evolving separately for 1300+ years, so the characters aren&#39;t all the same anymore.  Some kanji, even common ones, don&#39;t exist in Chinese, and others have a different stroke order (confounding the handwriting system if you enter the correct Japanese stroke order).   It&#39;s a good thing to use, but you can&#39;t depend on it for finding kanji, because a frustratingly high percentage of the time, it just won&#39;t work.</p>
<p>For some of the common kanji that aren&#39;t in Chinese and more detail on why they&#39;re not, see <a href="http://en.wikipedia.org/wiki/Chinese_character#Comparisons_of_Traditional.2C_Simplified_and_Kanji" rel="nofollow"></a><a href="http://en.wikipedia.org/wiki/Chinese_character#" rel="nofollow">http://en.wikipedia.org/wiki/Chinese_character#</a>&#8230; </p>
<p>Try entering the kanji for, e.g., common kanji like the ones for black, Buddha, and the &#8220;ki&#8221; in &#8220;genki&#8221; (and thousands of other words) on your iPhone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/comment-page-2/#comment-18164</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Fri, 09 Apr 2010 11:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.tofugu.com/?p=564#comment-18164</guid>
		<description><![CDATA[Sorry--click on my name to get to the page with the links to the app and the free dictionaries and instructions.  &lt;br&gt;&lt;br&gt;And, yup, Prof. Breen is indeed a cool guy.]]></description>
		<content:encoded><![CDATA[<p>Sorry&#8211;click on my name to get to the page with the links to the app and the free dictionaries and instructions.  </p>
<p>And, yup, Prof. Breen is indeed a cool guy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/comment-page-2/#comment-18165</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Fri, 09 Apr 2010 11:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.tofugu.com/?p=564#comment-18165</guid>
		<description><![CDATA[A much better version of Edict is the customized one at JLT.  For Japanese to English it&#039;s the same as the standard, searchable by kanji or kana.  But it&#039;s been heavily edited to be much better when searching English-to-Japanese.  For example, with the standard Edict, when you look up &quot;horse,&quot; you get a lot of irrelevant results up front--&quot;uma,&quot; the actual word for horse, comes up only after scrolling through quite a few screens--it&#039;s around the 40th result.  In the JLT version of Edict, it&#039;s the first.   Plus there&#039;s a version of Jim Breen&#039;s Kanjidic and Enamdict on the JLT site--and Kanjidic has been altered to show you stroke orders for all 6355 kanji, and to let you look up kanji directly (by entering kanji), by reading, and by SKIP order.  And there&#039;s a dictionary that shows you how to conjugate every verb in Edict (&quot;what&#039;s the past causative of &#039;hasamu&#039;?&quot;), and to enter a conjugated verb to find out what tense and what verb it is.  Plus you can add any dictionary in the standard EPWING format (Koujien, Daijirin, Kenkyusha, and a special version of Eijiro with yomigana added for every kanji compound, Genius, etc.).  Morever, the app that runs all these dictionaries, EBPocket,  doesn&#039;t have any of the problems you describe above--it works well.  Visit the page below for links to the app ($4.99), to download the free dictionaries, and for instructions for replacing the version of Edict that comes with the app (which has the same E-to-J problems you mention above) with the free JLT dictionaries.  Disclosure: I make the free dictionaries mentioned; I don&#039;t have anything to do with the app.]]></description>
		<content:encoded><![CDATA[<p>A much better version of Edict is the customized one at JLT.  For Japanese to English it&#39;s the same as the standard, searchable by kanji or kana.  But it&#39;s been heavily edited to be much better when searching English-to-Japanese.  For example, with the standard Edict, when you look up &#8220;horse,&#8221; you get a lot of irrelevant results up front&#8211;&#8221;uma,&#8221; the actual word for horse, comes up only after scrolling through quite a few screens&#8211;it&#39;s around the 40th result.  In the JLT version of Edict, it&#39;s the first.   Plus there&#39;s a version of Jim Breen&#39;s Kanjidic and Enamdict on the JLT site&#8211;and Kanjidic has been altered to show you stroke orders for all 6355 kanji, and to let you look up kanji directly (by entering kanji), by reading, and by SKIP order.  And there&#39;s a dictionary that shows you how to conjugate every verb in Edict (&#8220;what&#39;s the past causative of &#39;hasamu&#39;?&#8221;), and to enter a conjugated verb to find out what tense and what verb it is.  Plus you can add any dictionary in the standard EPWING format (Koujien, Daijirin, Kenkyusha, and a special version of Eijiro with yomigana added for every kanji compound, Genius, etc.).  Morever, the app that runs all these dictionaries, EBPocket,  doesn&#39;t have any of the problems you describe above&#8211;it works well.  Visit the page below for links to the app ($4.99), to download the free dictionaries, and for instructions for replacing the version of Edict that comes with the app (which has the same E-to-J problems you mention above) with the free JLT dictionaries.  Disclosure: I make the free dictionaries mentioned; I don&#39;t have anything to do with the app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/comment-page-2/#comment-16323</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Fri, 09 Apr 2010 05:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.tofugu.com/?p=564#comment-16323</guid>
		<description><![CDATA[I&#039;m kind of put off that iJisho claims you can use the Chinese handwriting input to enter kanji without mentioning that it doesn&#039;t work very well for a lot of kanji, and it doesn&#039;t work at all for many others, even some very common ones.   If you buy the app expecting to be able to enter kanji by handwriting, you&#039;re going to be frustrated.  Simply put, Chinese hanzi and Japanese kanji have been evolving separately for 1300+ years, so the characters aren&#039;t all the same anymore.  Some kanji, even common ones, don&#039;t exist in Chinese, and others have a different stroke order (confounding the handwriting system if you enter the correct Japanese stroke order).   It&#039;s a good thing to use, but you can&#039;t depend on it for finding kanji, because a frustratingly high percentage of the time, it just won&#039;t work.&lt;br&gt;&lt;br&gt;For some of the common kanji that aren&#039;t in Chinese and more detail on why they&#039;re not, see &lt;a href=&quot;http://en.wikipedia.org/wiki/Chinese_character#Comparisons_of_Traditional.2C_Simplified_and_Kanji&quot; rel=&quot;nofollow&quot;&gt;http://en.wikipedia.org/wiki/Chinese_character#...&lt;/a&gt; &lt;br&gt;&lt;br&gt;Try entering the kanji for, e.g., common kanji like the ones for black, Buddha, and the &quot;ki&quot; in &quot;genki&quot; (and thousands of other words) on your iPhone.]]></description>
		<content:encoded><![CDATA[<p>I&#39;m kind of put off that iJisho claims you can use the Chinese handwriting input to enter kanji without mentioning that it doesn&#39;t work very well for a lot of kanji, and it doesn&#39;t work at all for many others, even some very common ones.   If you buy the app expecting to be able to enter kanji by handwriting, you&#39;re going to be frustrated.  Simply put, Chinese hanzi and Japanese kanji have been evolving separately for 1300+ years, so the characters aren&#39;t all the same anymore.  Some kanji, even common ones, don&#39;t exist in Chinese, and others have a different stroke order (confounding the handwriting system if you enter the correct Japanese stroke order).   It&#39;s a good thing to use, but you can&#39;t depend on it for finding kanji, because a frustratingly high percentage of the time, it just won&#39;t work.</p>
<p>For some of the common kanji that aren&#39;t in Chinese and more detail on why they&#39;re not, see <a href="http://en.wikipedia.org/wiki/Chinese_character#Comparisons_of_Traditional.2C_Simplified_and_Kanji" rel="nofollow"></a><a href="http://en.wikipedia.org/wiki/Chinese_character#" rel="nofollow">http://en.wikipedia.org/wiki/Chinese_character#</a>&#8230; </p>
<p>Try entering the kanji for, e.g., common kanji like the ones for black, Buddha, and the &#8220;ki&#8221; in &#8220;genki&#8221; (and thousands of other words) on your iPhone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/comment-page-2/#comment-16320</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Fri, 09 Apr 2010 04:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.tofugu.com/?p=564#comment-16320</guid>
		<description><![CDATA[Sorry--click on my name to get to the page with the links to the app and the free dictionaries and instructions.  &lt;br&gt;&lt;br&gt;And, yup, Prof. Breen is indeed a cool guy.]]></description>
		<content:encoded><![CDATA[<p>Sorry&#8211;click on my name to get to the page with the links to the app and the free dictionaries and instructions.  </p>
<p>And, yup, Prof. Breen is indeed a cool guy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.tofugu.com/2008/08/06/jim-breen-on-the-iphone/comment-page-2/#comment-16321</link>
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Fri, 09 Apr 2010 04:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.tofugu.com/?p=564#comment-16321</guid>
		<description><![CDATA[A much better version of Edict is the customized one at JLT.  For Japanese to English it&#039;s the same as the standard, searchable by kanji or kana.  But it&#039;s been heavily edited to be much better when searching English-to-Japanese.  For example, with the standard Edict, when you look up &quot;horse,&quot; you get a lot of irrelevant results up front--&quot;uma,&quot; the actual word for horse, comes up only after scrolling through quite a few screens--it&#039;s around the 40th result.  In the JLT version of Edict, it&#039;s the first.   Plus there&#039;s a version of Jim Breen&#039;s Kanjidic and Enamdict on the JLT site--and Kanjidic has been altered to show you stroke orders for all 6355 kanji, and to let you look up kanji directly (by entering kanji), by reading, and by SKIP order.  And there&#039;s a dictionary that shows you how to conjugate every verb in Edict (&quot;what&#039;s the past causative of &#039;hasamu&#039;?&quot;), and to enter a conjugated verb to find out what tense and what verb it is.  Plus you can add any dictionary in the standard EPWING format (Koujien, Daijirin, Kenkyusha, and a special version of Eijiro with yomigana added for every kanji compound, Genius, etc.).  Morever, the app that runs all these dictionaries, EBPocket,  doesn&#039;t have any of the problems you describe above--it works well.  Visit the page below for links to the app ($4.99), to download the free dictionaries, and for instructions for replacing the version of Edict that comes with the app (which has the same E-to-J problems you mention above) with the free JLT dictionaries.  Disclosure: I make the free dictionaries mentioned; I don&#039;t have anything to do with the app.]]></description>
		<content:encoded><![CDATA[<p>A much better version of Edict is the customized one at JLT.  For Japanese to English it&#39;s the same as the standard, searchable by kanji or kana.  But it&#39;s been heavily edited to be much better when searching English-to-Japanese.  For example, with the standard Edict, when you look up &#8220;horse,&#8221; you get a lot of irrelevant results up front&#8211;&#8221;uma,&#8221; the actual word for horse, comes up only after scrolling through quite a few screens&#8211;it&#39;s around the 40th result.  In the JLT version of Edict, it&#39;s the first.   Plus there&#39;s a version of Jim Breen&#39;s Kanjidic and Enamdict on the JLT site&#8211;and Kanjidic has been altered to show you stroke orders for all 6355 kanji, and to let you look up kanji directly (by entering kanji), by reading, and by SKIP order.  And there&#39;s a dictionary that shows you how to conjugate every verb in Edict (&#8220;what&#39;s the past causative of &#39;hasamu&#39;?&#8221;), and to enter a conjugated verb to find out what tense and what verb it is.  Plus you can add any dictionary in the standard EPWING format (Koujien, Daijirin, Kenkyusha, and a special version of Eijiro with yomigana added for every kanji compound, Genius, etc.).  Morever, the app that runs all these dictionaries, EBPocket,  doesn&#39;t have any of the problems you describe above&#8211;it works well.  Visit the page below for links to the app ($4.99), to download the free dictionaries, and for instructions for replacing the version of Edict that comes with the app (which has the same E-to-J problems you mention above) with the free JLT dictionaries.  Disclosure: I make the free dictionaries mentioned; I don&#39;t have anything to do with the app.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
