Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Barry Warsaw
On Apr 18, 2014, at 03:07 AM, Stephen J. Turnbull wrote: >Getting it right by design ... well, that's why we need Mailman 3. And really, Python 3. The email package in Python 3.4 rocks. -Barry -- Mailman-Users mailing list Mailman-Users@python

Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Stephen J. Turnbull
I see you've already responded, but there are a few things I'd like to clarify. Laura Creighton writes: > But you and I could quite easily both want English(USA) as the > default language for our lists, but you also want us-ascii while I > want utf-8. The way things stand now, we cannot both

Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Laura Creighton
In a message of Thu, 17 Apr 2014 15:54:19 +0200, Laura Creighton writes: >In a message of Thu, 17 Apr 2014 05:41:15 -0700, Mark Sapiro writes: >>The issue is msg_footer is assumed to be in the character set of the >>list's language, us-ascii by default for English. I don't think Mailman >>does the

Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Mark Sapiro
On 04/17/2014 06:54 AM, Laura Creighton wrote: > In a message of Thu, 17 Apr 2014 05:41:15 -0700, Mark Sapiro writes: > > Now that my problem has gone from 'getting the EP footers to work' to > 'understanding what exactly is going on here'. And right now I do not > see why the charset for the lis

Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Barry Warsaw
On Apr 17, 2014, at 03:54 PM, Laura Creighton wrote: >Now that my problem has gone from 'getting the EP footers to work' to >'understanding what exactly is going on here'. And right now I do not >see why the charset for the lists' language has to be hard coded in >mm_cfg.py, nor why there has to

Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Laura Creighton
In a message of Thu, 17 Apr 2014 05:41:15 -0700, Mark Sapiro writes: >The issue is msg_footer is assumed to be in the character set of the >list's language, us-ascii by default for English. I don't think Mailman >does the right thing in this case. >From my perspective, the problem is that by havin

Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Mark Sapiro
On 04/17/2014 05:28 AM, Stephen J. Turnbull wrote: > > Mailman already has about 200 lines of logic to handle cases where the > footer charset is incompatible with the message's charset. Have you > tried simply changing the Python escape to a literal EN DASH in the > web interface? I hope Mailma

Re: [Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Mark Sapiro
On 04/17/2014 04:19 AM, Laura Creighton wrote: > > But unless I have overlooked something, there is no way to make a charset > change on a per-list basis through the mailman administrative interface. > Instead you have to edit mm_cfg.py Correct. > Even if I had root access on python.org, I wo

[Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Stephen J. Turnbull
Hi, Laura! Laura Creighton writes: > But the Europython mailing list is configured so that its messages > come out > > Content-Type: text/plain; charset="us-ascii" This isn't from the list or site configuration, this is from the poster's mail user agent (MUA). The mailing list does not cho

[Mailman-Users] Trying to understand charset encoding in mailman

2014-04-17 Thread Laura Creighton
I am trying to understand how charset encoding works, and I get the distinct idea that I must be missing one small, vital piece of information. Background: The problem arose as follows: Somebody changed the footer of the EuroPython Mailing list which is hosted at python.org to be: EuroPython 201