Re: [Mutt] #3040: charset difference between index browser and
- To: mutt-dev@xxxxxxxx
- Subject: Re: [Mutt] #3040: charset difference between index browser and
- From: Kyle Wheeler <kyle-mutt-dev@xxxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 16:05:37 -0500
- Cc: fleas@xxxxxxxx
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date: from:to:cc:subject:message-id:references:mime-version: content-type:in-reply-to; q=dns/txt; s=default; bh=qn5fyraVQ8uNA yHbzhXMi/z/Yvc=; b=FRQnSmncGWVs0mp7ierS1Te23L0NonYAk09njDIWLcq9b CToTzSlHj8OaROCSQTuc91F/gtYm/st9qk9UN5agaCjN76tXuU1k4AfdTH83vn0u 82Jx/u1jpwjWUcVwxd4NiI5Af2E/IwP0gGvPdkBbJsAdSsSpbnJ9OmwANdMepg=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=jsG4/wQrA6BIAEM8WRaH2zxGZQpgWcb1AtSKJ1+faBsCtRZ8QyE0PXg1jDRTBy/iwfEzFai0IUf2raQ/7NmUoCyeGMcy3jsnhCmEHNLM2NA4DYbl1JdSpvd8GxOWkA+gDwnDo2bNe/DHW2qmeA0oeKAR/24kO9zD/D9Ar/xHjE4=; h=Received:Received:Date:From:To:Cc:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <037.b4d3a5e597da310ee107a426b2fc4a0e@xxxxxxxx>
- List-post: <mailto:mutt-dev@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
- Mail-followup-to: mutt-dev@xxxxxxxx, fleas@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <037.b4d3a5e597da310ee107a426b2fc4a0e@xxxxxxxx>
- Sender: owner-mutt-dev@xxxxxxxx
- User-agent: Mutt/1.5.17 (2008-02-27)
On Tuesday, March 18 at 08:42 PM, quoth Mutt:
set assumed_charset=UTF-8
set charset=UTF-8//TRANSLIT
Do not set $charset. There are very few good reasons for it.
There is *never* a good reason to use UTF-8 and //TRANSLIT at the same
time.
Suppose my name (Miek Gieben) would contain some high unicode
codepoint character at the second position. In the index browser it
would be displayed as
M?ek Gieben
It's possible that your name is being mis-encoded in email, and so it
is taking various paths through mutt on the way to being displayed
based on whether mutt notices the problem or not.
My guess would be: make sure your name is properly encoded, and stop
setting your $charset manually.
This is not a bug in mutt; the proper venue for this question would be
the mutt-user mailing list.
~Kyle
--
The Son of man came eating and drinking, and they say, "Behold, a
glutton and a drunkard, a friend of tax collectors and sinners!" Yet
wisdom is justified by her deeds.
-- Matthew 11:19
Attachment:
pgp9Mv3o2Iju4.pgp
Description: PGP signature