[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SOLVED
From: |
Clément Pit--Claudel |
Subject: |
Re: SOLVED |
Date: |
Fri, 6 May 2016 08:32:20 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
On 2016-05-06 08:24, Yuri Khan wrote:
> No, Gmail sends normal “Content-Type: multipart/alternative”
> messages, where the first alternative is text/plain and uses
> conventional “>” quoting, and the second alternative is text/html,
> optionally encoded as quoted-printable, with <blockquote> quoting.
> The messages are valid w.r.t. RFC 2822 and RFC 2045, and the
> text/html payload is loosely well-formed HTML5.
I don't think so. When I look at the source of Kaushal's messages, the '>'
character is missing on the first line of each quoted section (see for example
his message <address@hidden>). Thus what should be rendered as the following is
actually as shown below in the message body:
(Intended rendering, as suggested by the blockquotes in the HTML version:)
> I suggest to change/add the docstring accordingly, because the new
> behavior is a radical change.
> I could provide a 'patch' for that[1]
That's great!
> , but not sure about the structure of
> that patch
(Actual rendering:)
>
> I suggest to change/add the docstring accordingly, because the new
behavior is a radical change.
>
> I could provide a 'patch' for that[1]
That's great!
, but not sure about the structure of
> that patch
Or is there an issue with Thunderbird's source rendering?
Clément.
signature.asc
Description: OpenPGP digital signature
- Re: SOLVED, (continued)
- Re: SOLVED, Uwe Brauer, 2016/05/05
- Re: SOLVED, Kaushal Modi, 2016/05/05
- Re: SOLVED, Uwe Brauer, 2016/05/06
- Re: SOLVED, Yuri Khan, 2016/05/06
- Re: SOLVED, Uwe Brauer, 2016/05/06
- SOLVED II (was: SOLVED), Uwe Brauer, 2016/05/06
- Re: SOLVED, Clément Pit--Claudel, 2016/05/06
- Re: SOLVED, Yuri Khan, 2016/05/06
- Re: SOLVED,
Clément Pit--Claudel <=
- Re: SOLVED, Eli Zaretskii, 2016/05/06