emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SOLVED


From: Eli Zaretskii
Subject: Re: SOLVED
Date: Fri, 06 May 2016 16:00:18 +0300

> From: Clément Pit--Claudel <address@hidden>
> Date: Fri, 6 May 2016 08:32:20 -0400
> Cc: Emacs developers <address@hidden>
> 
> 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?

Is this really relevant to Emacs?  If not, could you take this
discussion elsewhere?

Thanks.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]