From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] UTF-8 message sending patch
Date: Wed, 29 Apr 2009 15:38:23 -0700 [thread overview]
Message-ID: <1241044621-sup-9157@entry> (raw)
In-Reply-To: <1240861799-sup-787@colargol.tihlde.org>
Reformatted excerpts from Helge Titlestad's message of 2009-04-27:
> 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.
Thanks! Good timing on this; it was near the top of my todo list.
I will probably edit this a bit and merge it in as part of a bigger
utf-8 fixing branch.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-04-29 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 20:00 Helge Titlestad
2009-04-29 22:38 ` William Morgan [this message]
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=1241044621-sup-9157@entry \
--to=wmorgan-sup@masanjin.net \
/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