<<< Date Index >>>     <<< Thread Index >>>

Re: freebsd, mutt, unicode



* On Tue, Jan 17, 2006 mal content (artifact.one@xxxxxxxxxxxxxx) muttered:
> The headers on the email say:
> 
> Mime-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Disposition: inline
> Content-Transfer-Encoding: 8bit
> 
> This seems to be correct.

Yes. Sending should always work even in a non-utf aware terminal etc.
Does the message display correctly in a gui MUA?

> The message should read
> 
> Где ресторан, нравиться?

well whatever it says :)

> it actually says:

Displaying however is another story.

> I have set up my LC_* variables correctly

LC_CTYPE=en_US.utf8 for example. LC_CTYPE is the only locale variable
which matters in this case.

> and have set charset="utf-8" in .muttrc

Don't *set* charset, this can have bad side effects. Let mutt auto-detect it!

Here's my utf-8 howto:
  muttrc:
  Actually mutt's defaults should work out of the box in a utf
  environment.
  Here are a few little tweaks that i changed.
---[SNIP]---
  #you may want to add other locale charsets
  #koi8-r for example
  set send_charset="us-ascii:iso-8859-1:iso-8859-15:utf-8"

  #my configs are in iso. This is only relevant when you have non
  #ascii chars in the config
  set config_charset=iso-8859-15

  #DO NOT set charset!
  reset charset
---[SNIP]---

The important parts are the terminal, font and locales.
uxterm is a nice xterm wrapper which does mostly everything right. At
least for the terminal and locale part. You need to make sure it uses a
utf font:

alias uxterm='uxterm -fn 
-misc-fixed-medium-r-normal-*-15-140-75-*-c-*-iso10646-1'

HTH,

Michael
-- 
snafu = Situation Normal All F%$*ed up

PGP-Key-ID: 0xDC1A44DD
Jabber:     init[0]@amessage.de