On 2006-10-30 09:33:02 +0100, Anders Lennartsson wrote: > EMACS IN XTERM > > Now the problem is emacs in a terminal window. It does properly show > utf-8 characters when I open documents. But when I start to write it > does not correctly understand the Swedish characters from my keyboard, > which indicates some problem with keyboard setting or input or so. > > After opening a utf-8 encoded file with emacs -nw, C-h C produces the > output in [3]. > > Any tips or solutions to get utf-8 working for emacs -nw in xterm?
See http://www.vinc17.org/mutt/ (there's a section on Emacs for Mutt). The only character encoding problem I have is with Emacs as a terminal (in which Mutt can be started, useful for mailto URLs). But when Emacs is started in a terminal (I tried many, including xterm), there are no problems. > MUTT > > A related issue is mutt, which I use both on sid and sarge, and it > starts emacs in the xterm where it runs. In sarge (with utf-8 as > default) the settings for emacs are seen in [4]. But on sid mutt > starts emacs differently, see [5]. > > I don't understand where the differences come from as my .emacs are > identical for the two computers, and there seems to be no significant > differences in the site wide emacs settings. Probably something different in the default system configuration. Again, http://www.vinc17.org/mutt/ may help you. > BTW, is it really necessary to use the package mutt-utf8 to get > support for utf-8? I don't know. It no longer exists in testing/unstable. But I use my own patched version of Mutt (nothing special for UTF-8, though). > It seems to work and the characters show up nicely in normal mutt. I > think it my(?) configuration of emacs in a terminal window that is > the root cause of these problem. Yes, probably. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
