No, not me; I touched it last in a large merge, but it was added a year ago
by novalis:

https://dev.plone.org/collective/changeset/60727

Doesn't the listen codebase rfc822ify strings all the time with some library
function?  I don't have a checkout offhand but there must be some standard
way that the code is already using elsewhere.

egj

On Wed, May 6, 2009 at 2:49 PM, Robert Marianski
<[email protected]>wrote:

> I looked at that point in the code, and it looks like we're trying to
> adhere to an rfc. Ethan, maybe you can shed some light on it? It looks
> like you checked in that code.
>
> Robert
>
> On Wed, May 06, 2009 at 07:04:38AM +0300, Domas Monkus wrote:
> > Hi,
> > I've stumbled upon what I think is a small bug in listen. The problem is
> > visible when a user has unicode characters in his name and tries to post
> > a message on the list via the web frontend (not by sending an email).
> >
> > In this case all the unicode characters are removed from the name which
> > leaves the name illegible.
> >
> > The problem comes from browser/mail_archive_views.py : 253
> > (ArchiveNewTopicView.member_address) where all the characters are
> > removed.
> >
> > I believe this is a bug and though I am not sure how, I think it should
> > be fixed.
> >
> > Best regards,
> > Domas
> >
> >
> >
> > --
> > Archive:
> http://www.openplans.org/projects/listen/lists/listen-dev/archive/2009/05/1241582704571
> > To unsubscribe send an email with subject "unsubscribe" to
> [email protected].  Please contact
> [email protected] for questions.
> >
>

Reply via email to