<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Getting Kanji Working in Emacs: Mule-UCS Startup Hook</title>
	<link>http://regex.info/blog/2007-04-17/426</link>
	<description>Not a photo blog, but sometimes I play one on TV</description>
	<pubDate>Tue, 02 Dec 2008 20:28:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: Joe</title>
		<link>http://regex.info/blog/2007-04-17/426#comment-4096</link>
		<pubDate>Thu, 03 May 2007 03:29:37 +0000</pubDate>
		<guid>http://regex.info/blog/2007-04-17/426#comment-4096</guid>
					<description>Very nice.  I'd never had a problem with this in Fedora, but I recently decided to give the new Ubuntu feisty fawn distro a swing and was having a helluva time with emacs and funny characters.  I got other Japanese specific encodings working fine, euc-jp and shift-jis, but finding out why Japanese utf8 wasn't displaying properly was becoming a huge pain.  I've been able to input things properly, but I couldn't get them to display!

&#62;&#62;"Next time, try googling for an answer in Japanese.
Keywords used this time: emacs utf-8 漢字入力"

Instead, I think "emacs  utf-8 漢字　表示" makes more sense, since my problem at least was displaying, not inputting Japanese utf-8.　The article is also about display, not input...

Anyway that's my 2cents.  Thanks again!</description>
		<content:encoded><![CDATA[<p>Very nice.  I&#8217;d never had a problem with this in Fedora, but I recently decided to give the new Ubuntu feisty fawn distro a swing and was having a helluva time with emacs and funny characters.  I got other Japanese specific encodings working fine, euc-jp and shift-jis, but finding out why Japanese utf8 wasn&#8217;t displaying properly was becoming a huge pain.  I&#8217;ve been able to input things properly, but I couldn&#8217;t get them to display!</p>
<p>&gt;&gt;&#8221;Next time, try googling for an answer in Japanese.<br />
Keywords used this time: emacs utf-8 漢字入力&#8221;</p>
<p>Instead, I think &#8220;emacs  utf-8 漢字　表示&#8221; makes more sense, since my problem at least was displaying, not inputting Japanese utf-8.　The article is also about display, not input&#8230;</p>
<p>Anyway that&#8217;s my 2cents.  Thanks again!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Andy</title>
		<link>http://regex.info/blog/2007-04-17/426#comment-3986</link>
		<pubDate>Wed, 18 Apr 2007 00:28:33 +0000</pubDate>
		<guid>http://regex.info/blog/2007-04-17/426#comment-3986</guid>
					<description>Hello again,

Gotcha! I'm not into programming at all, though I do know about text editors like vi, vim, and emacs from openSUSE installed on my thinkpad. Most of my digging around is done in dictionaries.

Cheers ...</description>
		<content:encoded><![CDATA[<p>Hello again,</p>
<p>Gotcha! I&#8217;m not into programming at all, though I do know about text editors like vi, vim, and emacs from openSUSE installed on my thinkpad. Most of my digging around is done in dictionaries.</p>
<p>Cheers &#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Andy</title>
		<link>http://regex.info/blog/2007-04-17/426#comment-3985</link>
		<pubDate>Tue, 17 Apr 2007 23:33:37 +0000</pubDate>
		<guid>http://regex.info/blog/2007-04-17/426#comment-3985</guid>
					<description>Hi Jeffrey,

Next time, try googling for an answer in Japanese.

Keywords used this time: emacs utf-8 漢字入力

Result and jackpot: http://softsupport.seesaa.net/article/25598905.html

Tadaa! Two months of grief reduced to twenty-seconds, just like that.

&lt;span class='jfriedl'&gt;Oh, I did searches similar to that, and it's such a search that lead to the solution. Most of the two months was trying to figure out where the problem was.... I didn't know whether it was a problem with my Mac or its Terminal app, my shell settings, the Debian Linux box I was connected to, its emacs install, or my 'screen' install or settings. I was futzing with installing new versions of emacs, old versions of emacs, reading the man page for 'stty' a dozen times. As far as I could tell, emacs wasn't getting the input (I wondered whether it put the tty into some weird kind of state I'd never heard of), so to test this, I built a version of emacs that displayed the raw bytes of keyboard input as they came in, and indeed, emacs &lt;i&gt;was&lt;/i&gt; getting the input. From that point, it took 15 minutes of digging around to solve the problem, and another 15 minutes to write the post. &#8212;Jeffrey&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p>Hi Jeffrey,</p>
<p>Next time, try googling for an answer in Japanese.</p>
<p>Keywords used this time: emacs utf-8 漢字入力</p>
<p>Result and jackpot: <a href="http://softsupport.seesaa.net/article/25598905.html" rel="nofollow">http://softsupport.seesaa.net/article/25598905.html</a></p>
<p>Tadaa! Two months of grief reduced to twenty-seconds, just like that.</p>
<p><span class='jfriedl'>Oh, I did searches similar to that, and it&#8217;s such a search that lead to the solution. Most of the two months was trying to figure out where the problem was&#8230;. I didn&#8217;t know whether it was a problem with my Mac or its Terminal app, my shell settings, the Debian Linux box I was connected to, its emacs install, or my &#8217;screen&#8217; install or settings. I was futzing with installing new versions of emacs, old versions of emacs, reading the man page for &#8217;stty&#8217; a dozen times. As far as I could tell, emacs wasn&#8217;t getting the input (I wondered whether it put the tty into some weird kind of state I&#8217;d never heard of), so to test this, I built a version of emacs that displayed the raw bytes of keyboard input as they came in, and indeed, emacs <i>was</i> getting the input. From that point, it took 15 minutes of digging around to solve the problem, and another 15 minutes to write the post. &mdash;Jeffrey</span>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: William</title>
		<link>http://regex.info/blog/2007-04-17/426#comment-3981</link>
		<pubDate>Tue, 17 Apr 2007 17:58:22 +0000</pubDate>
		<guid>http://regex.info/blog/2007-04-17/426#comment-3981</guid>
					<description>Thanks very much for funding that.  I do not know if that change in emacs was triggered as a result of the release of etch being just about ready to be released or not, but this. Is a good caveat to watch for next time I dwell in Japanese input.  Thanks!</description>
		<content:encoded><![CDATA[<p>Thanks very much for funding that.  I do not know if that change in emacs was triggered as a result of the release of etch being just about ready to be released or not, but this. Is a good caveat to watch for next time I dwell in Japanese input.  Thanks!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
