From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] new in svn: rfc2047 header decoding, and charset conversion
Date: Mon, 18 Jun 2007 08:47:50 -0700 [thread overview]
Message-ID: <1182181055-sup-7065@south> (raw)
RFC2047 headers and MIME message parts with Content-Type headers are now
converted to the local character set (default utf8 if not set). This
should work immediately for new messages. In order to see these changes
on messages already in the index, you'll need to:
1. delete any entries in people.txt and contact.txt that are
RFC2047-encoded; and
2. run sup-sync --all --all-sources
If you see warnings in the Sup log about decoding, that means iconv
couldn't convert the original message to your character set. It's a
little picky and apparently doesn't offer anything more fine-grained
than "encode everything or raise an exception". We just use the original
message as is, as we've been doing all along, in that case.
On my Debian box with LANG=en_US.utf-8, running Sup in gnome-terminal, I
can now see accented characters. Yay! Haven't yet tried wide characters.
--
William <wmorgan-sup at masanjin.net>
reply other threads:[~2007-06-18 15:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1182181055-sup-7065@south \
--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