Am 08.07.2013 08:29, schrieb Rimas Kudelis:
2013.07.08 02:48, Michael Heydekamp wrote:
Am 03.07.2013 08:35, schrieb Rimas Kudelis:
2013.07.03 00:20, Michael Heydekamp wrote:
I tend to believe that the HTML part is supposed to be displayed as-is, that's why it's HTML in the first place. It's the sender's job to format it the way they want the receiver to see it.
The sender can't do anything else than what he gets when he's quoting a (plain text) message: He will have one or more ">" in front of every quoted line. Which is (in his sent HTML message) then being HTML encoded as one or more ">".
So what exactly should he "format" there...??
Upon HTML decoding ">" to ">", the ">" should be recognized as a quote char when displaying it, IMO.
What am I missing?
Hm... so you are suggesting that during quoting of a plain-text message in an HTML message, no style conversion should happen ("the sender can't do anything" - why is that?), yet you're also suggesting that Roundcube should freely re-format any HTML messages it gets if it sees an < at the beginning of a line? This doesn't sound logical to me.
Hmm, probably you're misunderstanding me. I'm not saying that Roundcube should re-format anything. Nor should the HTML user be forced to re-format anything.
I'm currently replying to your message in plain text format. Quoted lines are preceded with the common quote char ">". See screenshot, while I'm typing this.
Now I'm switching to the HTML editor...
As you can see, quoted lines are still preceded with the quote char ">". Are you saying that I, just because I'm a HTML user now, should have to re-format all these quoted lines? And even if so, HOW should I re-format them...? Remove all those "> ", ">> ", ">>> " and so on, and replace them with colours or whatever??
No, of course I'm continuing with composing the message without doing any re-formatting. And that will end up with what I described: Quoted lines/paragraphs will not be displayed in Roundcube as quoted lines. See this message...
I'll repeat myself, but I believe that HTML is supposed to be shown as-is. Unlike plain text, HTML has all the means necessary to store information about nice formats and colors in messages, so at least in my opinion, there is no reason why the receiver's MUA should do anything fancy about displaying HTML messages (well, anything other than stripping scripts and disabling images). If the sender's MUA is incapable to format HTML messages in a way the sender wants it displayed by the receiving party, then what's the point for the sender to use HTML
A quote char is a quote char is a quote char - IMO also in HTML messages. It just needs to be detected as one.
And with regards to "what's the point for the sender to use HTML" - this you shouldn't really ask me. ;-) I haven't a clue, this is my very first HTML e-mail.
I'll be sending this message twice - first as HTML, then as plain text. Decide yourself what you like better. And that's why I'm suggesting that quote chars should (after HTML decoding) be treated as quote chars in HTML messages as well.
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany