Ivan Van Laningham wrote: > > I think something else is going on, besides just the <LF> only line > ending. I'm using two versions of T-Bird, 1.5 and 2.0 something, and > both display the message concerned the same way, all crammed together on > a single line. I think there must be some encoding issue. It probably > is some configuration issue with T-Bird, but I've not been able to find it.
I can't find any relevant configuration setting in T-Bird, and I don't see the problem in T-Bird 2.0.0.4 with a utf-8 charset base64 encoded message I received through a test list. The message contained the following ---------------------------------- This should be a unicode encoded message. Throw in a few “funny” chars To get encoding ---------------------------------- The lines of dashes are separate lines and in between are a line of text, an empty line, a second line of text, a second empty line and a third line of text. I'm sending this in utf-8 charset (I hope), and it should come from the list encoded base64, and I expect it will display as described in my T-Bird 2.0.0.4. What do you see? -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
