Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Helge Titlestad <helgedt@tihlde.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] [PATCH] detect and set charset on text/* attachments
Date: Thu, 21 Jun 2012 22:26:19 +0200	[thread overview]
Message-ID: <1340310366-sup-4562@tihlde.org> (raw)

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


             reply	other threads:[~2012-06-22  0:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 20:26 Helge Titlestad [this message]
2012-06-22  8:48 ` Gaute Hope
2012-06-22 10:29   ` Helge Titlestad
  -- strict thread matches above, loose matches on Subject: below --
2009-10-19 14:07 Helge Titlestad
2009-11-03 17:16 ` William Morgan
2009-11-03 19:23   ` Helge Titlestad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1340310366-sup-4562@tihlde.org \
    --to=helgedt@tihlde.org \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox