* [sup-talk] new in svn: rfc2047 header decoding, and charset conversion
@ 2007-06-18 15:47 William Morgan
0 siblings, 0 replies; only message in thread
From: William Morgan @ 2007-06-18 15:47 UTC (permalink / 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>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-06-18 15:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-06-18 15:47 [sup-talk] new in svn: rfc2047 header decoding, and charset conversion William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox