Corporate Information | Software | Support | Contact Us
Corporate Information
Software
Messenger Pro
Messenger Pro Downloads
Beta and Archived Downloads
Evaluate
Support
Messenger Pro FAQ
Messenger Pro Change Log
Messenger Pro (Windows/Linux/Mac) Mailing List Archive
Messenger Pro (RISC OS) Mailing List Archive
Bug Tracker
Contact Us

Re: Forwarding HTML emails

From:Richard Mellish Date:1 Aug 2021 11:39
In Reply To: Re: Forwarding HTML emails (Richard Porter)
Replies: Re: Forwarding HTML emails (Chris Hughes)
Re: Forwarding HTML emails (Richard Porter)

Richard Porter <ricp@...> said:

> On 31 Jul 2021 Richard Mellish  wrote:

>> Those of us who still prefer plain text emails are nowadays in a minority,
>> with the world and his wife using HTML by default.

>> MPro usually copes adequately with HTML-only emails, showing an
>> approximation as text plus a pseudo-attachment of the HTML which you can
>> view in a browser. But it gets messy when you need to forward one to other
>> people. One option is to forward only the plain text, but any features of
>> the HTML such as coloured or bold text, which might be significant, are
>> lost and there are often spurious characters resulting from passage
>> between OSs and incomplete handling of Unicode. Another option is to
>> forward the whole thing, but the recipients then see an attachment called
>> Email.htm, which some are suspicious of.

>> How do others on here deal with it?

> I normally just send the plain text part and delete the html part if
> present. Some of the html is horrendous, often two orders of magnitude
> larger than plain text. If we banned html messages excepting attached html
> files the internet would be a great deal faster.

> Many email clients and webmail systems make a complete mess of generating
> plain text. I get a newsletter from the local council in which the text
> part is a solid block with no paragraph separation at all. Some mailers
> just send a cop-out text part - blank or just a link to a web site.

> Worst of all are those that put html (usually an incomplete page) in the
> text/plain part. If necessary I go to the html part and let Messenger Pro
> do a much better job of converting it to plain text. It still leaves in
> some escaped characters, zero width non-joiners, etc.

I agree with all of that. To keep my original posting short if I didn't 
mentione another mess than I see occasionally, so I will mention it now. 
An emailshot has perfectly sensible content in the HTML part but whoever 
sends it out must be blissfully unaware of the plain text part, which 
contains a recycled out-of-date message, instructions intended for the 
person drafting the mailshot, or even complete twaddle.

Richard

______________________________________________________________________
This message was sent via the messenger-l mailing list
To unsubscribe, mail messenger-l+unsubscribe@...



© 2024 intellegit ltd. - info@intellegit.com