Re: More on non-ascii chars in headers
- To: mutt-users@xxxxxxxx
- Subject: Re: More on non-ascii chars in headers
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Tue, 25 Sep 2007 09:02:55 -0500
- Cc: Eyolf Østrem <eyolf@xxxxxxxxxxx>
- 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:content-transfer-encoding:in-reply-to; q=dns/txt; s=default; bh=UCugoJJOfeULGlW4wlBfKrR8gqg=; b=l10mh7gH7F7YVCyBDPm2CKgJt7FjmhoI641ZXli6UC09lfbrDQzYa0sr4TNfRSB1yqYXIVHuPwksCBHiba0k97vPctj9OqXxdLoGDus/7IsH11scsfyvl+BQJ/xOSil8stGMjjkh6pYmg1eNwhnbsFzkPRbnQpyT8MqVXDM7Fpw=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=AqK1qlDy6GSPD8Z0ocgQXTGfqYj3ADhIybAgu1p8afFfwY73B0D0ZANHGe8Yz0bkufnman8P5gBfCTCT0cIonBzMeNwXlTagRLIdgM2Tiv5+6Mq05HIzpyy+7uJ8KIP5Nwy/NZXj6Geo1uhRsXHBEPrGethyLbX8BSeFET0RSOk=; h=Received:Received:Date:From:To:Cc:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:In-Reply-To:User-Agent;
- In-reply-to: <20070925075912.GB5959@eyo>
- 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, Eyolf Østrem <eyolf@xxxxxxxxxxx>
- References: <20070925075912.GB5959@eyo>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.16 (2007-09-10)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, September 25 at 10:03 AM, quoth Eyolf Østrem:
> Eyolf =?iso-8859-1?Q?=D8strem?= <eyolf () oestrem ! com>
>
>Not so nice to look at... Is there still some setting I should
>make/change, or is this down to marc.info's inability to handle
>unicode characters?
The answer is, unfortunately, no. There's no way to specify
"alternatives" in your From header. Plus, even if there was, it's
doubtful that marc.info would support them, given that it doesn't seem
interested or capable of decoding the existing RFC. You have to either
send your name correctly encoded and just realize that old and/or
broken software (like marc.info) is going to get it wrong OR convert
your name into all-ascii for sending to mailing lists (i.e. Oestrem).
~Kyle
- --
I created a cron job to remind me of the Alamo.
-- Arun Rodrigues
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFG+RUPBkIOoMqOI14RAjCqAKC2PCYgX8LuO3XuVusnV6z8fwIohACfTNPr
9f+Jm2WLhDCqCWeU1QIJyDk=
=yeiM
-----END PGP SIGNATURE-----