Re: wrong charset
- To: mutt-users@xxxxxxxx
- Subject: Re: wrong charset
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Wed, 13 May 2009 09:07:10 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=0/9puKvo1jemKBeN/avFrT72ek8=; b=JI1j B4AsQelsM6A8WbS6PN7rHZPmVmVoiRG2rA/0wmcQgfSU95mTrfxVfbZNIVVqkaYE QxTjJmUsgGeIcfX3qEmdypI8UNVKsb1BDYW5IHXcDmyPqtoN/wsJ6K+eaz1Uiau9 fDAIWGMA8hH5llf/nJaJLa2+rT/Cnji/LH8qrZA=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=mVdpzVOFD66szpHZSNHbh1oTe2EoOEajUBMsrg6QtUFajyS8H1Xa5lvyQCar099cwUQQE4gr+oocwvXUBy9mZmZOlhriyQGqG7oCcQTyIXIlbuxU/7S03TlOrrE9GpXuUeSYHRXw2dZd0ZDaH96rGLnnVzL6MqDtJX4k7mmAgXA=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20090513121603.GB9037@xxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20090513121603.GB9037@xxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.19 (2009-04-29)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Wednesday, May 13 at 09:16 AM, quoth Luis A. Florit:
> I should have said this first, but if I switch the console encoding
> to utf8, then the message is properly displayed. So, the utf8
> 'realm' works ok. Hence, mutt is transforming an iso8859-1 message
> into a (correct) utf8 one, despite the fact that my xterm is
> iso8859-1, and despite the value of charset variable. Other programs
> like VIM work fine.
The reason for that is because Vim handles all the character
manipulation internally. That means it has to be far more complicated,
because it has to have its own concept of character set coded into it
(this is often known as "reinventing the wheel"). Mutt, on the other
hand, relies on system libraries to handle most string operations, and
so is more sensitive to the locale settings (because that's what the
system libraries rely on). For whatever reason, your Nokia does not
come with ISO-8859-1 locales. Vim doesn't care, because it has the
definition of ISO-8859-1 compiled into it, but mutt does care, because
it can only output into character sets that your system will allow it
to.
~Kyle
- --
If I were you, I'd run!
- -- Mesh-Head
If you were me, you'd be good-looking.
- -- the Six-String Samurai
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJKCtQNAAoJECuveozR/AWeMzEP/3O56Rm9u/p0HmLxNuM4JZI0
3qaQCc/3Fq1i46agl/i2Nw1pJ9OLz2znqihTRghy36lW2r8duKjPrr3GxYMznkp0
skQjOU4p8ooXaKrMnf6gmdmWoVYYkmbS2J8kV+jv06qNUevu2DBb1ouCcVkV+iki
GulOrWBWkzkYSGzshwtcX/rYceWLlQlSGjvZY008myPVHKF50yYOe09dP1Pwzq45
23lqTLpw/D3cMlewOuUbW/13jcXxLBkzpawbI7xDkev9joijUkWBQ783wp08DToe
11DZdHQpaxdf6r4kFnpu0sY5Py/Wlpvy4a3wAM9PXPile9MR5IT6FgPR0FRhjwQ8
P/ESnEY4xBUiWMkI6/qBYFWHP2S5OsKA7U+4vOT358a7GgEcS2j6nV6nvYUP7Egw
cOBl+FbJ2YqV3pI8FB9Oxf+bvYtkud/rBrPioKUEJWRtNvODd4kaHTaUgCWTK4Ms
rWUAhOpgOcsfzt8SeYXwO+2msUqkUyh85eaSyYAYUs6JSFx/kkIuGaW2gcOGa5qx
W9pQ78reE0NNAv+H/gPj4IATWsRDTiNw6Uigo8vMzZY/bcP032jGZOg48fZeMfOn
wu+czjoequ9zTyd16AN1ao53Ah/fZLmWSi7pldexEA5Esn3zHkudEogZ2FT3SCdO
b/Tj5rGoMKOkTPwQzWzj
=5JM4
-----END PGP SIGNATURE-----