Re: [Evolution] Replying to HTML formatted emails



On Thu, 2004-01-08 at 11:47, David Woodhouse wrote:
On Wed, 2004-01-07 at 16:34 +0000, Pete Biggs wrote:
I don't like HTML emails, so I have my default set to not send mail
using HTML.  However, I'm not so anti-HTML mail that I won't deal with
mail that people send me in HTML!  Consequently, sometimes I have to
reply to it.  Now some of the mail I get is from people like Ebay and
the formatting of their automatically generated HTML email is full of
tables - but when I reply to it the *text* in the composer still retains
the table structure. 

These people sent you HTML mail. Why do you care what your reply looks
like? Just send TeX back.

Actually, what I usually do is switch to 'view email source' and quote
their HTML noise back at them. i.e.

On Wed, 2004-01-07 at 16:34 +0000, Clueless idiot wrote:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html;
CHARSET=UTF-8"><META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9">
</HEAD><BODY><!--+GtkHTML:<DATA class="ClueFlow" key="orig" value="1">

I'm very sympathetic to that view!!  When I used to use elm all the time
I did it lots.  However, the emails I'm having most trouble with are
those generated by Ebay - when someone pays me for instance, Ebay sends
me an automatically generated email with their comments in that appears
to be from the buyer, so I reply to it - but it's virtually impossible
to construct a sensibly formatted reply in Evo because of the format of
the original email - and it's not the fault of the person who I'm
sending the email to, so it's a bit unfair to send them a load of quoted
HTML!  To be fair to Ebay, they do use multipart text/html, so text only
MUAs can deal with it, but in Evo I can't easily get access to the text
part to reply to it.

P.

-- 
Pete Biggs :{)       pete physchem ox ac uk     pete biggs chem ox ac uk
  Phone: 01865 275490 (Work)    01865 275410 (Fax)     pete biggs org uk




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]