From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org, yuri.v.khan@gmail.com
Subject: Re: SOLVED
Date: Fri, 06 May 2016 16:00:18 +0300 [thread overview]
Message-ID: <83shxvfijh.fsf@gnu.org> (raw)
In-Reply-To: <572C8ED4.4080404@gmail.com> (message from Clément Pit--Claudel on Fri, 6 May 2016 08:32:20 -0400)
> From: Clément Pit--Claudel <clement.pit@gmail.com>
> Date: Fri, 6 May 2016 08:32:20 -0400
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> 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 <CAFyQvY0-gMVfOTbCvCm7JUZEf2NaWKkfn-EDk2MSM_WTvJVKQw@mail.gmail.com>). 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.
prev parent reply other threads:[~2016-05-06 13:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 20:01 vc-hg modeline changed Uwe Brauer
2016-05-05 9:15 ` SOLVED (was: vc-hg modeline changed.) Uwe Brauer
2016-05-05 11:26 ` Kaushal Modi
2016-05-05 16:10 ` SOLVED Uwe Brauer
2016-05-05 16:18 ` SOLVED Kaushal Modi
2016-05-05 16:41 ` SOLVED Andreas Schwab
2016-05-05 20:12 ` SOLVED Uwe Brauer
2016-05-06 6:27 ` SOLVED Eli Zaretskii
2016-05-05 20:50 ` SOLVED Uwe Brauer
2016-05-05 21:33 ` SOLVED Kaushal Modi
2016-05-06 7:53 ` SOLVED Uwe Brauer
2016-05-06 9:28 ` SOLVED Yuri Khan
2016-05-06 10:29 ` SOLVED Uwe Brauer
2016-05-06 10:45 ` SOLVED II (was: SOLVED) Uwe Brauer
2016-05-06 12:10 ` SOLVED Clément Pit--Claudel
2016-05-06 12:24 ` SOLVED Yuri Khan
2016-05-06 12:32 ` SOLVED Clément Pit--Claudel
2016-05-06 13:00 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83shxvfijh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=yuri.v.khan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).