Re: [Mailman-Users] Encoding problems

2008-06-19 Thread Mark Sapiro
Allan Odgaard wrote: On 19 Jun 2008, at 00:24, Mark Sapiro wrote: You may consider it a bug if you wish. It is intentional (but still perhaps wrong) that the message is coerced to the character set of the list's preferred language when msg_header and/or msg_footer are added. I meant in the

Re: [Mailman-Users] Encoding problems

2008-06-18 Thread Allan Odgaard
On 18 Jun 2008, at 02:49, Mark Sapiro wrote: [...] Into `/etc/python2.5/sitecustomize.py`. This is despite proper setup of `LC_CTYPE` on the system. Seems to me Mailman should use the encoding of the current locale, not this site-wide Python default encoding (settable by root only). I am aware

Re: [Mailman-Users] Encoding problems

2008-06-18 Thread Mark Sapiro
Allan Odgaard wrote: I don’t think Mailman should use `sys.getdefaultencoding()`. See http://wiki.python.org/moin/DefaultEncoding. I think instead `locale.getdefaultlocale()` should be used for the CLI commands. Since sys.getdefaultencoding() is going away, we'll have to do something ;)

Re: [Mailman-Users] Encoding problems

2008-06-18 Thread Allan Odgaard
On 18 Jun 2008, at 16:09, Mark Sapiro wrote: [...] The process of adding the list header and/or footer to the message attempts to add these to a text/plain body by coercing the body and the header/footer to unicode, concatenating them and then coercing back to the original body charset. If the

Re: [Mailman-Users] Encoding problems

2008-06-18 Thread Mark Sapiro
Allan Odgaard wrote: On 18 Jun 2008, at 16:09, Mark Sapiro wrote: [...] The process of adding the list header and/or footer to the message attempts to add these to a text/plain body by coercing the body and the header/footer to unicode, concatenating them and then coercing back to the

Re: [Mailman-Users] Encoding problems

2008-06-18 Thread Allan Odgaard
On 19 Jun 2008, at 00:24, Mark Sapiro wrote: So should I consider it a bug that setting list encoding to utf-8 will (in my experience) _always_ produce (base 64 encoded) utf-8 letters, when both header/footer and letter itself sent to list is ASCII? You may consider it a bug if you wish. It

Re: [Mailman-Users] Encoding problems

2008-06-17 Thread Mark Sapiro
Allan Odgaard wrote: Some of my subscribers have accents and similar in their name and I had to do the following post install to have Mailman properly work with these: ## CLI In order to get `list_members -f «list»` to properly output non-ASCII user names I had to put the following:

[Mailman-Users] Encoding problems

2008-06-16 Thread Allan Odgaard
Some of my subscribers have accents and similar in their name and I had to do the following post install to have Mailman properly work with these: ## CLI In order to get `list_members -f «list»` to properly output non-ASCII user names I had to put the following: import sys

Re: [Mailman-Users] Encoding problems

2008-06-16 Thread Brad Knowles
On 6/17/08, Allan Odgaard wrote: For the web page forms to accept non-ASCII I had to put this: add_language('en', 'English', 'utf-8') Into `/etc/mailman/mm_cfg.py`. I think utf-8 should be the default because even on an English list, you can use non-ASCII punctuation, glyphs, and many

Re: [Mailman-Users] Encoding problems

2004-11-05 Thread Asbjørn Ulsberg
On Wed, 27 Oct 2004 18:02:11 -0700, Mark Sapiro [EMAIL PROTECTED] wrote: The text in the info box is not HTML despite the confusing documentation. It is text only. Any included , or characters are escaped. Although I have not edited this page myself, I understand it so as the text has not been

Re: [Mailman-Users] Encoding problems

2004-11-05 Thread Mark Sapiro
Asbjørn Ulsberg wrote: On Wed, 27 Oct 2004 18:02:11 -0700, Mark Sapiro [EMAIL PROTECTED] wrote: The text in the info box is not HTML despite the confusing documentation. It is text only. Any included , or characters are escaped. The above statement is more or less correct for 2.1.4, but

Re: [Mailman-Users] Encoding problems

2004-11-05 Thread Asbjørn Ulsberg
On Fri, 5 Nov 2004 15:53:07 -0800, Mark Sapiro [EMAIL PROTECTED] wrote: The text in the info box is not HTML despite the confusing documentation. It is text only. Any included , or characters are escaped. The above statement is more or less correct for 2.1.4, but not for 2.1.5 Okay. Perhaps an

[Mailman-Users] Encoding problems

2004-10-28 Thread Asbjørn Ulsberg
Hi, I just wonder if anyone could explain to me what has gone wrong on the following Mailman listinfo page and what needs to be done to fix it: url: http://mailman.efn.no/mailman/listinfo/open-standard I would actually like to go into the source code and not only fix the encoding problem, but

[Mailman-Users] Encoding problems

2004-10-27 Thread Asbjørn Ulsberg
Hi, I just wonder if anyone could explain to me what has gone wrong on the following Mailman listinfo page and what needs to be done to fix it: url: http://mailman.efn.no/mailman/listinfo/open-standard I would actually like to go into the source code and not only fix the encoding problem, but also

Re: [Mailman-Users] Encoding problems

2004-10-27 Thread Mark Sapiro
Asbjørn Ulsberg wrote: Hi, I just wonder if anyone could explain to me what has gone wrong on the following Mailman listinfo page and what needs to be done to fix it: url: http://mailman.efn.no/mailman/listinfo/open-standard The text in the info box is not HTML despite the confusing