public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Treating changes in quoted nesting as paragraph breaks
Date: Thu, 19 Sep 2019 12:49:39 -0400	[thread overview]
Message-ID: <93cba32f-bf2d-bec8-bb96-58be123e3a0b@reagle.org> (raw)


I often get email with nested quoting that looks like this:

```
> This is a quoted line.
> > This is a nested quoted line. Wrapping the first line won't
> > touch this one.
> And continuing with a third line.
```

When I process such quotes with pandoc, with wrapping, it sees it
as a single paragraph and makes a mess of it -- understandably.

Would it be possible to process these a bit smarter?


             reply	other threads:[~2019-09-19 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 16:49 Joseph Reagle [this message]
     [not found] ` <93cba32f-bf2d-bec8-bb96-58be123e3a0b-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-09-19 18:29   ` John MacFarlane

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93cba32f-bf2d-bec8-bb96-58be123e3a0b@reagle.org \
    --to=joseph.2011-t1oy19wchswdnm+yrofe0a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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.
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 NNTP newsgroup(s).