From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eg@gaute.vetsj.com>
Received: from localhost (cD18A5BC1.dhcp.bluecom.no. [193.91.138.209])
        by mx.google.com with ESMTPS id o5sm20424239lbg.5.2012.06.22.01.38.40
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 22 Jun 2012 01:38:41 -0700 (PDT)
Content-Type: text/plain; charset=UTF-8
From: Gaute Hope <eg@gaute.vetsj.com>
To: Sup Talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] detect and set charset on text/* attachments
In-reply-to: <1340310366-sup-4562@tihlde.org>
References: <1340310366-sup-4562@tihlde.org>
Date: Fri, 22 Jun 2012 10:48:41 +0200
Message-Id: <1340354870-sup-6182@qwerzila>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Hi,

Would be interested; but where's the patch ? ;)

- Gaute

Excerpts from Helge Titlestad's message of 2012-06-21 22:26:19 +0200:
> I got some feedback from non-suppers that my utf-8 text attachments were
> messed up. When I checked they (the MIME headers) lacked any info on charset,
> which I believe should be set for text/*.
> 
> Here's a patch that uses the chardet gem to (try to) detect the appropriate charset
> and sets it in the Content-Type header.