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

Re: setting default encodings



 On Wednesday, April 13, 2005 at 3:17:03 PM -0400, Paul Tremblay wrote:

> 1) If I drop the LC_TYPE line, then I cannot read eamils with UTF-8.

    Probably the LC_CTYPE value is already exported before, somewhere
else in startup scripts. Drop this too, and check with "locale" and
"locale charmap" that all is clean.


> 2) When I reply to emails that are in utf-8, mutt sets the encoding as
> latin1.

    That's fine if your full reply (quotes included) contains only chars
existing in Latin-1. Mutt always sends in best adapted first necessary
and sufficient charset.

    You don't really want all your outgoing emails to be UTF-8 encoded:
Minimal charset gives better chances to be correctly read anywhere by
anyone on any platform.


> 3) If I forward an email to myself that is utf-8, the characters come
> out funny. For example, you (or was it someone else) posted an email
> with the unicode star. This appears as a star in my email. I forward
> the emails to myself, and make sure I send it as utf-8, 8-bit. (I have
> to do the utf-8 part manually.)

    Problem here: You should not have to <edit-type> to UTF-8 manually,
because Mutt should have choosed this charset itself. BTW just after
change, do you « Convert to utf-8 upon sending? ([yes]/no): »?

    Something is breaking Mutt's automation: Do you have any non-Ascii
chars in signature, attribution, or in Muttrc/.muttrc? Do you have
iconv-hooks? What is your iconv version? Is your editor unconditionally
saving UTF-8 files?


> a funny character followed by \202 or some other number.

    And « cannot read », yes... You could use a little more accuracy. Is
it "â\230\205" (a circumflex, 230, 205)? Do you happen to use HP-UX?


Bye!    Alain.
-- 
set honor_followup_to=yes in muttrc is the default value, and makes your
list replies go where the original author wanted them to go: Only to the
list, or with a private copy.