<div id="_htmlarea_default_style_" style="font:10pt arial,helvetica,sans-serif">Since it seems to annoy him so much I'll
just keep on using it. <br><br><br>On Fri, 29 Feb 2008 14:12:51 -0600<br> "Samir M. Nassar"
<samir.nassar+tclug@steamedpenguin.com> wrote:<br>> On Friday 29 February 2008 13:41:24 Brian Dunnette
<br>>wrote:<br>> <br>>> Every time you use a mail client that doesn't gracefully <br>>>deal with
HTML,<br>>> another Ron Paul story appears on Reddit.<br>> <br>> My mail client deals just fine with HTML. I
don't have <br>>my mail client set to <br>> automagically parse HTML. I also make sure that when I <br>>use a
mail client that <br>> I don't send out HTML mail. Mail clients read and <br>>display text just fine. <br>>
They even have decent conventions for quoting mail.<br>> <br>> Attached are html.txt and message.txt<br>>
<br>> message.txt weighs in at 553 bytes<br>> html.txt weighs in at 256 bytes<br>> <br>> If the formatting
had added anything of worth, fine. But <br>>in this case the text <br>> was not marked up. You know, the Markup in
Hyper-text <br>>Markup Language? Why <br>> would you need to markup anyway? Since you are throwing <br>>around
graceful <br>> clients, how graceful is a mail client when it can parse <br>>HTML but can't turn <br>> a lonely
URL into a link?<br>> <br>> If you notice, the HTML itself sucks sweaty goat balls, <br>>all repetitive break
<br>> tags. If you are sending HTML mail, why again is the <br>>mail client using font <br>>
declarations?<br>> <br>> Lastly it is a pretty long standing convention to not <br>>abuse mailing lists by
<br>> sending HTML mail.<br>> <br>> Samir M. Nassar<br>> <br>> PS- Thank you for changing the subject
line, something I <br>>neglected to do.<br><br></div>