Mark Sapiro writes: > > Ah, interesting. However, what is the canonical approach then? Is the > > mailman web interface supposed to recode everything to UTF on the fly? > > Because, firefox thinks, that the pages are in UTF-8, presumably because > > that's what the server says. > > Mailman includes the tag > > <META http-equiv="Content-Type" content="text/html; charset=xxx"> > > where xxx is Mailman's charset for the language. The browser shouls > accept that.
Technical Note: Except that as far as I know if there is an HTTP Content-Type field in the header, and that specifies charset=yyy, that takes precedence over the META HTTP-EQUIV specification. That is an unusual problem, but if you've tried everything else, and not figured it out, that's a possibility. > The problem is if you change Mailman's charset for the > language to utf-8 but don't recode templates, messages and list > attributes as utf-8, you will include non-utf-8 encodings in text > declared as utf-8. This is most likely the problem, as mail itself is a mishmash of charsets, and Mailman draws text for display from a blizzard of sources, which Mailman itself has to *assume* are consistent. ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
