From: helgedt@tihlde.org (Helge Titlestad)
Subject: [sup-talk] UTF-8 message sending patch
Date: Mon, 27 Apr 2009 22:00:44 +0200 [thread overview]
Message-ID: <1240861799-sup-787@colargol.tihlde.org> (raw)
Hi,
I just installed sup and noticed that it didn't play extremely well
with utf-8 out of the box.
http://sup.rubyforge.org/wiki/wiki.pl?UTF8 together with the String
hack from http://www.nabble.com/UTF-8-woes-td21598658.html#a21598658
fixed the viewing parts (I think), but it's still unacceptable to
send raw utf-8 in email headers.
So I fixed it with another little hack (to edit-message-mode.rb),
which sets Content-Transfer-Encoding to 8-bit and more importantly
tries to convert any utf-8 headers to quoted printable.
I think the patch (attached) fixes my problems, but it's probably far
from complete. It doesn't detect non-utf8-but-still-illegal-strings,
it assumes every header except Subject is an address, and so on.
Any feedback is welcome. (:
--
alge
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-utf8-message-sending.patch
Type: application/octet-stream
Size: 1904 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090427/6cae2b53/attachment.obj>
next reply other threads:[~2009-04-27 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 20:00 Helge Titlestad [this message]
2009-04-29 22:38 ` William Morgan
2009-05-28 15:11 ` William Morgan
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=1240861799-sup-787@colargol.tihlde.org \
--to=helgedt@tihlde.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