On Friday, February 28, 2025 1:35:07 AM MST Jonathan Dowland wrote:
> On Wed Feb 26, 2025 at 6:21 PM GMT, Soren Stoutner wrote:
> > I have composed this email without an arbitrary column wrap, so that
> > those receiving it can see how it is handled by their various clients
> > and devices.
> 
> I didn't notice (until Marc pointed it out) because my client (aerc)
> re-wraps mails, even non-format=flowed ones, although I think there's a
> risk the process could corrupt the message. I haven't spotted that
> happening yet.
> 
> I double-checked whether your message was format=flowed or not, and
> noticed you sent it multipart with HTML, which (given the topic) I found
> amusing.

I think that is probably Kmail’s default.  Nothing in this discussion is about 
HTML vs. plain 
text.  I don’t really mind if Kmail sends an HTML part as long as it also sends 
a plain text 
part, and it probably makes life easier for a lot of the people I communicate 
with outside 
of Debian circles.

As a funny side note, when I first started actively contributing to Debian I 
opened a 
lengthy bug report.  I started typing it in reportbug, but the complexity of 
the report and 
the desire for spell checking caused me to compose it in Kate instead.  When I 
was done I 
copied and pasted it into the open reportbug and sent it off.

The resulting text was not wrapped.  I didn’t think anything about it at the 
time, but I got a 
complaint from someone responding to the bug report saying it was hard to quote 
my 
HTML text.  I thought to myself, “I didn’t know reportbug produced HTML text?”  
Of course, 
it hadn’t.  Rather, the person who was having problems with unwrapped text 
assumed it 
was some sort of HTML problem.

It was because of that I set Kmail to wrap text at 80 columns.  And I make sure 
and 
manually wrap text in reportbug.  Until now, when this itch got big enough I 
thought it 
was time it should be scratched.

-- 
Soren Stoutner
so...@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to