On Wed, May 18, 2011 at 04:33:49PM +0000, Grant Edwards wrote: > > The last problem I've encountered is that in the past, some systems > > were still defaulting to non-UTF-8 charsets, and even if you set your > > LANG properly your X session was started with a non-unicode > > environment. > > That could be it. I don't have LANG set to an UTF locale when I start > X. Every time I've tried to enable UTF support across-the-board, I've > run into so many problems that I switched back. Mutt is the only > program where I've run into any need for UTF, so I set LANG to a UTF > locale before starting the terminals in which I run mutt.
Hmm... It sounds like you're already doing this, but what fixed it for me (before I got around to fixing the default locale) was to set my locale in my shell, then from that shell start a new xterm with -u8 (specify unicode mode, no longer needed) and then run mutt (or whatever) from that new terminal. If that's what you're doing, and it still doesn't work, I'm at a bit of a loss... My last suggestion would be to reinstall your system, and choose a unicode environment from the get-go. That's pretty extreme, but it's the default these days, and I have not had any Unicode issues of any kind on systems I've installed in the last, oh, 5 years or so (installed with unicode locales from the start). At least, none that weren't specifically related to entering Korean characters... but even those have been worked out for the last several years. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgphgCxpzhPnN.pgp
Description: PGP signature
