Re: [Mutt] #3033: text_enriched_handler and UTF-8 (and charsets as
- To: mutt-dev@xxxxxxxx
- Subject: Re: [Mutt] #3033: text_enriched_handler and UTF-8 (and charsets as
- From: Kyle Wheeler <kyle-mutt-dev@xxxxxxxxxxxxxx>
- Date: Mon, 18 Feb 2008 16:19:17 -0600
- 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=uBGF61E5a+4sC th7NnjTws8HnrM=; b=brAeEFhrm2IsvHjF11u5HdiqALoPMGlKgnt6YiTmJ9DxJ wbpCWfENu9Z31ecbp7Et6yDmfMkG9QPp9I5D4IekId5YZHY4SCTx//Y9opoGQ4w5 9R9Ka6nKlASTVktNRi5WX49JwujnQOxr3hnNWVQsRS6myALVggG8Y3eTEa+qS0=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=ETXM3QXXnS3mXLZsxkHVylgkaMQ32jJ/RIDHG7JRqJX37/YLHIhLSgOTsN+HkWu+hCDq3xF7e5ugaWKaPdxwwoaIMsS74wYIVAseb7naSQEZjRbSwzbeSsbWVd4OFZb8Dbi+F6t4/ArnXCb/ASVgE2+/TNtvenzZSYr89JN9GiA=; 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: <045.622bfcafe7fe653a0b6eeceb9eada35d@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: <036.6fd40b79d8348769489bc350175ac965@xxxxxxxx> <045.622bfcafe7fe653a0b6eeceb9eada35d@xxxxxxxx>
- Sender: owner-mutt-dev@xxxxxxxx
- User-agent: Mutt/1.5.17 (2008-01-14)
On Monday, February 18 at 09:09 PM, quoth Mutt:
This has had me riddled for quite some time now as well. Even if I
set LC_CTYPE=de_DE.iso885915 (or similar, like "@euro"), I need to
tell mutt about it with "set charset=iso-8859-15". Or am I
overseeing something?
Mutt gets its charset from the output of nl_langinfo(CODESET) (if you
have the langinfo.h header). Otherwise, it simply assumes iso-8859-1.
So I'd say you should investigate that function. Here's a simple test
program:
#include <locale.h>
#include <langinfo.h>
#include <stdio.h>
int main()
{
setlocale(LC_CTYPE, "");
printf("%s\n", nl_langinfo(CODESET));
return 0;
}
See what that C program prints out, and do what you must to make it
print out the right thing (check the setlocale and nl_langinfo man
pages).
For what it's worth, my system doesn't recognize de_DE.iso885915. It
DOES recognize de_DE.ISO8859-15, though. When I run
`locale -a | grep de_DE`, all I see as options are:
de_DE
de_DE.ISO8859-1
de_DE.ISO8859-15
de_DE.UTF-8
Run that command (`locale -a | grep de_DE`) to see what your system
supports, and set LC_CTYPE to one of those.
~Kyle
--
When we blindly adopt any religion, political system, or literary
dogma, we become automatons. We cease to grow.
-- Anais Nin
Attachment:
pgp0s2tjy20q4.pgp
Description: PGP signature