Hey Domas,
Sorry for the slow response. I tried the patch you suggested on a local/dev
install of Listen. It resulted in mangled display of usernames on the web
interface -- apparently that
browser/mail_archive_views.py:ArchiveNewTopicView.member_address function is
used by the browser views as well as the email that's sent out.
A simple `sender_name.decode('utf8')` seems to work, though. Some
underlying mechanism must already be doing the re-encoding of non-ASCII
characters in the "from" header, because the sender's name is properly
displaying both on the web interface and in the generated email.
I've committed this to Products.listen/branches/0.6 and will make a 0.6.3
release shortly. I've done various unicode fixes on the 0.6 branch of
Listen (which is what I'm still using) -- but I'm somewhat reluctant to
merge them to trunk yet, since I'm not dogfooding trunk *and* haven't been
adding regression tests alongside the bugfixes.
If you're using the 0.7.1 release or trunk, I can try to send you a single
patch diff with these fixes if that would be helpful to you.
egj
On Thu, May 7, 2009 at 2:02 AM, Domas Monkus <[email protected]> wrote:
> Shouldn't this be used:
>
> from email.Header import Header
> str(Header(unicode(sender_name), header_charset))
>
> as described in http://mg.pov.lt/blog/unicode-emails-in-python.html ?
>
> Domas
>
>
>
> --
> Archive:
> http://www.openplans.org/projects/listen/lists/listen-dev/archive/2009/05/1241676196942
> To unsubscribe send an email with subject "unsubscribe" to
> [email protected]. Please contact
> [email protected] for questions.
>
>
--
Archive:
http://www.coactivate.org/projects/listen/lists/listen-dev/archive/2009/07/1247686109919
To unsubscribe send an email with subject "unsubscribe" to
[email protected]. Please contact
[email protected] for questions.
