Differences between revisions 1 and 2
Revision 1 as of 2013-05-05 20:29:00
Size: 649
Editor: msapiro
Comment:
Revision 2 as of 2015-02-01 03:34:51
Size: 893
Editor: msapiro
Comment: Added downside note.
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:

The one known downside of doing this is that Python's email library which is used by Mailman will base64 encode charset=utf-8 message bodies which makes the raw message body impossible to read by eye or search with simple tools like grep.

Mailman's character set for English is us-ascii. This causes non-ascii characters in posts and message headers and footers and other places to be replaced by question marks and/or numeric HTML entities in various contexts if the web interface and in plain format digests. This can be avoided by changing Mailman's character set for English to UTF-8. This has not been done in the GNU Mailman distribution for mainly superstitious reasopns, but it is believed to be safe. This is done by placing the line

add_language('en', 'English (USA)', 'utf-8', 'ltr')

in mm_cfg.py and restarting Mailman.

The one known downside of doing this is that Python's email library which is used by Mailman will base64 encode charset=utf-8 message bodies which makes the raw message body impossible to read by eye or search with simple tools like grep.

MailmanWiki: DOC/4.90 My list's moderator interface and plain format digests have garbled non-ascii. Change English charset to utf-8. (last edited 2021-04-20 19:15:54 by msapiro)