[Bug 1643210] Re: 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char

[Mark Sapiro]

This is an area where there is no one right answer. I have the display
name as a unicode, so how do I encode it for the header. I don't think
it should ever be encoded in the character set of the poster's language
because this is for a message to be sent to all list members, plus there
is no guarantee that the poster's display name as encoded by the sending
MUA was even encoded in Mailman's charset for the poster's language if
the poster is even a member, and there is no guarantee that the
translation of the 'via' can even be properly encoded in the charset of
the poster's language.

Further, there is no guarantee that the poster's display name can be
properly encoded in the charset of the list's preferred language either.

The most reasonable encoding of unicode that guarantees no loss of
information is utf-8, and any MUA that recognizes RFC 2047 encodings at
all should be able to handle utf-8 encodings.

Even if there are MUA's that can properly decode RFC 2047 encodings in,
e.g., iso-2022-jp but not utf-8, I think there are as many problems with
trying to encode the original display name in the list's charset as
there are with utf-8 encoding. I recognize that what I've done is a
compromise, but I think it's as good as any.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1643210

Title:
  'from_is_list' does not RFC2047 encode correctly when translation
  contains non-ascii char

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1643210/+subscriptions