On Monday, March 3, 2025 2:28:38 PM MST Stephan Verbücheln wrote: > Am Montag, dem 03.03.2025 um 13:38 -0700 schrieb Soren Stoutner: > > Also, as I mentioned elsewhere in this thread, this is not a > > discussion about the merits of HTML vs plain text. As long as emails > > to the mailing list contain a plain text part, I know of no problem > > caused by them also containing an HTML part, which the receiving MUA > > is welcome to ignore. > > The rules say “Please don't send your messages in HTML,” they do not > say “Please also add plain text to your messages.” > > It bloats up the message. > > But the more serious problem: Everyone actually has to verify that both > message parts have the same content for any important message, which > are both signed by PGP.
Interesting. I guess that text could be interpreted as “Do not send an HTML part, even if you also send a plain text part.” If that is the general understanding of the meaning of that section, then I think we ought to start a separate discussion about changing the text to be explicit that it is OK to send an HTML part as long as there is also a plain text part. However, I would appreciate it if this discussion were not hijacked to discuss HTML vs. plain text. This discussion is only about whether sending MUAs should be required to wrap plain text at a particular column. > > All of the subsequent emails I have sent as part of this discussion > > have been wrapped at 80 characters inline with the current mailing > > list code of conduct. > > They are wrapped in a silly and broken way if you take a look at the > message source. I agree. Having the sending MUA wrap text creates problems, even with efforts like format=flowed that try to hint to the receiving MUA how to unwrap the text. Hence, I propose that we change the expectation so that the sending MUA is not expected to wrap text. I believe it is the only solution that makes technical sense because 1) the sending MUA does not know the screen width of the receiving device, and 2) different receiving devices and users have wildly different width needs, and there is no single column width the sending MUA can use that works well on all receiving devices. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
