Re: [sup-talk] [PATCH] detect and set charset on text/* attachments

2012-06-22 Thread Gaute Hope
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.
___
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


Re: [sup-talk] [PATCH] detect and set charset on text/* attachments

2012-06-22 Thread Helge Titlestad
Excerpts from Gaute Hope's message of Fri Jun 22 10:48:41 +0200 2012:
 Would be interested; but where's the patch ? ;)

Hah, sorry guys. Someone tried to send an email from my sup last night[1],
and managed to re-send this ld mail instead. I think the utf-8 stuff
was fixed a long time ago. (=

-- 
alge
[1]: Yeah, alcohol was involved. 
___
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


Re: [sup-talk] [PATCH] detect and set charset on text/* attachments

2009-11-03 Thread William Morgan
Reformatted excerpts from Helge Titlestad's message of 2009-10-19:
 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/*.

After reviewing the RFCs, yeah, I think you're basically right. The
charset parameter is not required to be set for text/* mime types, but
if it's unset, the part is assumed to be us-ascii.

 Here's a patch that uses the chardet gem to (try to) detect the
 appropriate charset and sets it in the Content-Type header.

Although I don't relish adding yet another gem dependency, I think this
is the right approach.

It looks like the chardet gem is unmaintained. But someone decided to
make their own special version called rchardet which is completely
equivalent version but *is* maintained. (What is it with these goddamn
ruby people.)

I suggest we use rchardet instead of chardet. Would you like to change
the patch? If not, I will get to it at some point.

 Please tell me if I should use some different way of sending
 patches... This git flow is a bit new to me. (=

Nope, this is perfect. Thanks!
-- 
William wmorgan-...@masanjin.net
___
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk