On Jun 3, 2008, at 9:36 AM, Louis Proyect wrote:
But really, if the archives are rendering format-flowed as a run-on
line (i.e., they are marking it up as preformatted text, e.g using
"<pre>") then they really need to be fixed to not do that... hardly
anyone (including me?) honours the 78-character width rule any more
with hard returns.
Archiving software generally does not allow such tailoring. What
gives you the impression that it does?
Despite being written in Python ;-), Mailman is a fairly decent piece
of software, so I would have guessed they would handle these things
right. I just checked one more thing: while my mailer does set Content-
Type to format=flowed (telling the reader side mail client to cause
the text to flow), Yahoo WebMail (which Sabri uses) doesn't seem to,
setting Content-Type to just text/plain. Which is not surprising from
Yahoo and I heartily second your suggestion to Sabri to get the hell
away from Yahoo (I believe you put it more politely ;-) -- I
personally think webmail should be banned except for emergency/mobile
use... if you want to read/send mail use a mail client not a web
browser!).
Here's what is happening (I think): the Mailman archiver wraps the
entire message in <pre> tags (to preserve text formatting, I suppose).
Yahoo WebMail sends the message out as one continuous line so it gets
rendered as such. My mailer sends the text format=flowed i.e., it adds
a space and newline/carriage-return at the end of each line, so the
<pre> renders it correctly.
Given that Mailman is Python, we can hack it to be cleverer about this
sort of thing... that's what I meant in my earlier message.
--ravi
_______________________________________________
pen-l mailing list
[email protected]
https://lists.csuchico.edu/mailman/listinfo/pen-l
