Bugzilla

Henry, just try this: Reply to a long email, and interleave (!) comments within the quote, at multiple points, i.e. reply to specific parts of the quote, and insert your reply in the middle of the quote. That's the "Internet" way to reply.
1) Outlook is not capable of that
2) Our plaintext editor allows it, but it's hard to do, because it doesn't re-wrap the quoted lines, so you can end up in very unfortunate linebreaks in your quote. Manually adjusting the linebreaks in the quote then becomes a major hassle. Worse, if you do it wrong, the software no longer recognizes it as quote, and the recipient sees saw ">" instead of a blue bar and wrapping quotes.
3) In our HTML composer, you continue to see nice vertical blue quote bars, instead of the raw ">", even while you are editing, same nice display as when you read mails. Our HTML composer then allows you to just place the cursor anywhere in the quote, hit return, and it breaks the quote into 2 halves at that point, and you can interleave the comment. When you do that, we can automatically re-wrap quotes, e.g. use linebreaks where appriopriate, because we can differentiate between hard and soft linebreaks in the original plaintext email. That is particularly helpful when there are multiple nested quotes, and that avoids the "comb" effect that Outlook creates when the quote level in plaintext is too deep.

And this is just about quoting, which is an critical everyday feature for many of our users. But there are many other details in the plaintext handling that only our HTML composer can do, which is why it's the best way to send plaintext emails.

I'd say we have hands-down the best plaintext sending and receiving capabilities - but only when using the HTML composer. That's why this combination is important.

Can we *please* not re-open this entire complicated topic every time we touch something?

Henry, just try this: Reply to a long email, and interleave (!) comments within the quote, at multiple points, i.e. reply to specific parts of the quote, and insert your reply in the middle of the quote. That's the "Internet" way to reply.
1) Outlook is not capable of that
2) Our plaintext editor allows it, but it's hard to do, because it doesn't re-wrap the quoted lines, so you can end up in very unfortunate linebreaks in your quote. Manually adjusting the linebreaks in the quote then becomes a major hassle. Worse, if you do it wrong, the software no longer recognizes it as quote, and the recipient sees raw ">" instead of a blue bar and wrapping quotes.
3) In our HTML composer, you continue to see nice vertical blue quote bars, instead of the raw ">", even while you are editing, same nice display as when you read mails. Our HTML composer then allows you to just place the cursor anywhere in the quote, hit return, and it breaks the quote into 2 halves at that point, and you can interleave the comment. When you do that, we can automatically re-wrap quotes, e.g. use linebreaks where appriopriate, because we can differentiate between hard and soft linebreaks in the original plaintext email. That is particularly helpful when there are multiple nested quotes, and that avoids the "comb" effect that Outlook creates when the quote level in plaintext is too deep.

And this is just about quoting, which is an critical everyday feature for many of our users. But there are many other details in the plaintext handling that only our HTML composer can do, which is why it's the best way to send plaintext emails.

I'd say we have hands-down the best plaintext sending and receiving capabilities - but only when using the HTML composer. That's why this combination is important.

Can we *please* not re-open this entire complicated topic every time we touch something?

Henry, just try this: Reply to a long email, and interleave (!) comments within the quote, at multiple points, i.e. reply to specific parts of the quote, and insert your reply in the middle of the quote. That's the "Internet" way to reply.
1) Outlook is not capable of that
2) Our plaintext editor allows it, but it's hard to do, because it doesn't re-wrap the quoted lines, so you can end up in very unfortunate linebreaks in your quote. Manually adjusting the linebreaks in the quote then becomes a major hassle. Worse, if you do it wrong, the software no longer recognizes it as quote, and the recipient sees raw ">" instead of a blue bar and wrapping quotes. (That is suboptimal. Therefore, the plaintext composer is ironically suboptimal for composing normal plaintext emails. But of course some people prefer it, for ASCII arts and other reasons.)
3) In our HTML composer, you continue to see nice vertical blue quote bars, instead of the raw ">", even while you are editing, same nice display as when you read mails. Our HTML composer then allows you to just place the cursor anywhere in the quote, hit return, and it breaks the quote into 2 halves at that point, and you can interleave the comment. When you do that, we can automatically re-wrap quotes, e.g. use linebreaks where appriopriate, because we can differentiate between hard and soft linebreaks in the original plaintext email. That is particularly helpful when there are multiple nested quotes, and that avoids the "comb" effect that Outlook creates when the quote level in plaintext is too deep.

And this is just about quoting, which is an critical everyday feature for many of our users. But there are many other details in the plaintext handling that only our HTML composer can do, which is why it's the best way to send plaintext emails.

I'd say we have hands-down the best plaintext sending and receiving capabilities - but only when using the HTML composer. That's why this combination is important.

Can we *please* not re-open this entire complicated topic every time we touch something?

Henry, just try this: Reply to a long email, and interleave (!) comments within the quote, at multiple points, i.e. reply to specific parts of the quote, and insert your reply in the middle of the quote. That's the "Internet" way to reply.
1) Outlook is not capable of that
2) Our plaintext editor allows it, but it's hard to do, because it doesn't re-wrap the quoted lines, so you can end up in very unfortunate linebreaks in your quote. Manually adjusting the linebreaks in the quote then becomes a major hassle. Worse, if you do it wrong, the software no longer recognizes it as quote, and the recipient sees raw ">" instead of a blue bar and wrapping quotes.
3) In our HTML composer, you continue to see nice vertical blue quote bars, instead of the raw ">", even while you are editing, same nice display as when you read mails. Our HTML composer then allows you to just place the cursor anywhere in the quote, hit return, and it breaks the quote into 2 halves at that point, and you can interleave the comment. When you do that, we can automatically re-wrap quotes, e.g. use linebreaks where appriopriate, because we can differentiate between hard and soft linebreaks in the original plaintext email. That is particularly helpful when there are multiple nested quotes, and that avoids the "comb" effect that Outlook creates when the quote level in plaintext is too deep.

And this is just about quoting, which is an critical everyday feature for many of our users. But there are many other details in the plaintext handling that only our HTML composer can do, which is why it's the best way to send plaintext emails.

I'd say we have hands-down the best plaintext sending and receiving capabilities - but only when using the HTML composer. That's why this combination is important.

Can we *please* not re-open this entire complicated topic every time we touch something?