[fpc-devel] HTML e-mails in the list (Was: Re: {$push} and {$pop} on trunk [2024/02/13] for aarach64 doen't work)

[Tomas Hajny]

On 2024-02-16 10:06, Michael Van Canneyt via fpc-devel wrote:
> On Fri, 16 Feb 2024, Hairy Pixels via fpc-devel wrote:
> 
>> His email looks good to me. Much easier to see code with formatting.
>> 
>> Who doesn't have email clients with HTML support these days? I can't 
>> imagine how old your system must be to not have this.
> 
> I don't have HTML support in my mail program. My mail program is text 
> based.
> 
> HTML in mail is for 99.99% of cases a waste of bandwidth. I care about
> the content of a message, not about the markup.

@Michael - thanks, I'm sure there are others, possibly having HTML 
support but still preferring plain text e-mails for various reasons.

Since I triggered this discussion, I'd like to stop it before it evolves 
to a lengthy discussion about something which is not on topic on this 
list - if somebody feels a necessity to continue, fpc-other is the right 
place. Anyway - the particular message of the original poster was 
broken, possibly as a result of the mailing list processor adding the 
usual footer to it (I cannot check the culprit easily and I don't intend 
to try doing it) resulting in issues even with rather up to date e-mail 
clients supporting HTML. In particular, there was an empty plain text 
section in the e-mail containing just the footer. When responding to it 
with a very up to date mobile e-mail client (obviously supporting HTML 
e-mails), the original message was not quoted, because the client 
preferred the plain text version (which is a very reasonable default, 
especially on a mobile device). When displaying the message in another 
client (open-source webmailer, obviously also supporting HTML e-mails), 
parts of the message were displayed mixed with the footer.

As a moderator of this list, I _recommend_ everybody to use plain-text 
e-mails, or at least to configure the e-mail client to send both 
plain-text and HTML version of the outgoing messages. It isn't a strict 
requirement, but please understand that doing otherwise may result in 
issues.

Thanks

Tomas
(one of FPC mailing list moderators)