Wrong encoding in moderation request mails with Mailman 2.1.15
If a mail held for moderation has a subject encoded in UTF-8 the subject is not correctly displayed in the mail to the moderator and in the web interface. This is not a big issue but I nevertheless want to mention it. Do newer 2.x versions still have this behavior or is it already fixed?
Dipl.-Inform(FH) Peter Heitzer, peter.heitzer@rz.uni-regensburg.de
On 6/8/16 8:19 AM, Peter Heitzer wrote:
If a mail held for moderation has a subject encoded in UTF-8 the subject is not correctly displayed in the mail to the moderator and in the web interface. This is not a big issue but I nevertheless want to mention it. Do newer 2.x versions still have this behavior or is it already fixed?
I'm not sure what you are saying.
Suppose we have a message with
Subject: =?utf-8?Q?Try_this_=C4=93?=
Are you saying the subject is displayed literally as
=?utf-8?Q?Try_this_=C4=93?=
or are you saying it is displayed as
Try this ?
If the former, it's a bug, but I don't see that in current Mailman 2.1.22+
If the latter, that's the expected behavior because the character (ē) doesn't exist in the character set of the list's preferred language. Both the admindb web pages and the notice to the admin are encoded in the character set of the list's preferred language. For English, that is us-ascii, so non-ascii characters can't be displayed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 06/09/2016 at 18:37, Mark Sapiro <mark@msapiro.net> wrote: On 6/8/16 8:19 AM, Peter Heitzer wrote: If a mail held for moderation has a subject encoded in UTF-8 the subject is
not correctly displayed in the mail to the moderator and in the
web interface. This is not a big issue but I nevertheless want to mention it. Do newer 2.x versions still have this behavior or is it already fixed?
I'm not sure what you are saying.
Suppose we have a message with
Subject: =?utf-8?Q?Try_this_=C4=93?=
Are you saying the subject is displayed literally as
=?utf-8?Q?Try_this_=C4=93?=
or are you saying it is displayed as
Try this ?
If the former, it's a bug, but I don't see that in current Mailman 2.1.22+
If the latter, that's the expected behavior because the character (ē) doesn't exist in the character set of the list's preferred language. Both the admindb web pages and the notice to the admin are encoded in the character set of the list's preferred language. For English, that is us-ascii, so non-ascii characters can't be displayed. It is the latter. If I set the language to german, I get the umlauts displayed correctly. So it is the expected behavior although at least for the web pages I would have expected to get the correct display of the subject.
Dipl.-Inform(FH) Peter Heitzer, peter.heitzer@rz.uni-regensburg.de
On 06/10/2016 05:17 AM, Peter Heitzer wrote:
It is the latter. If I set the language to german, I get the umlauts displayed correctly. So it is the expected behavior although at least for the web pages I would have expected to get the correct display of the subject.
If you want to avoid this issue on lists whose preferred language is English and you have access to the server, you can change Mailman's character set for English by putting
add_language('en', 'English (USA)', 'utf-8')
in mm_cfg.py. The downside of doing this is that message body parts that have Mailman added msg_header or msg_footer will be base64 encoded.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Peter Heitzer