From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Markdown -> plain: How to preserve blockquotes?
Date: Mon, 4 Sep 2017 21:53:18 -0700 [thread overview]
Message-ID: <20170905045318.GE3765@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <fb9edf5e-3b0d-48b9-b10e-29f738a80987-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
+++ Francisco Lopes [Sep 04 17 11:52 ]:
> My last message was moderated, did I say anything wrong?
No, Google does that automatically on occasion, for reasons
that are generally opaque to me. I just unfroze your
message.
Pandoc's 'plain' output tries to reproduce the conventions
used in Project Gutenberg's plain text books. That doesn't
use `>` for quotes; rather, it uses indentation to come
close to the look of an actual printed book, and that's
what we do too.
The ` ` is a bug, though, which I'm about to fix.
In markdown you need something between a list and an
indented code block, or the indented block gets interpreted
as a continuation paragraph in the last list item. To
prevent that we insert an HTML comment or (if raw HTML is
disabled) a ` `. But of course this isn't necessary
in `plain` output.
next prev parent reply other threads:[~2017-09-05 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 5:16 Francisco Lopes
[not found] ` <b9e503e1-de59-4086-8104-64f32c8bfa5f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-03 6:53 ` Kolen Cheung
[not found] ` <d5636ec4-4c36-4514-a87a-3622e37d4986-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-03 12:36 ` Francisco Lopes
[not found] ` <cd94eef0-e89b-4aa2-969e-17cf6bb99162-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-04 1:58 ` Kolen Cheung
[not found] ` <8e1e0a64-7e87-4dbd-b669-0b55854fe110-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-04 8:33 ` Francisco Lopes
[not found] ` <e364ab5a-9752-47ce-ad05-9ece6e099b77-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-04 9:36 ` Kolen Cheung
[not found] ` <eaa32942-b318-456e-9ed6-7db797e050de-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-04 13:53 ` John Muccigrosso
2017-09-04 16:21 ` Francisco Lopes
2017-09-04 18:52 ` Francisco Lopes
[not found] ` <fb9edf5e-3b0d-48b9-b10e-29f738a80987-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-05 4:53 ` John MacFarlane [this message]
[not found] ` <20170905045318.GE3765-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-09-05 5:20 ` Francisco Lopes
[not found] ` <6ec4d317-8de4-476d-86c5-91438eb47729-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-05 5:28 ` Francisco Lopes
[not found] ` <ae3ba6b6-616a-4cb5-8bb2-be45b575d54e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-05 12:16 ` Kolen Cheung
[not found] ` <d6d7afde-883b-43da-9727-4ce24a08a43f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-05 18:02 ` Francisco Lopes
[not found] ` <9d2b4cdb-b236-42bd-baea-ff53da0ca1ed-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-05 18:17 ` John MacFarlane
[not found] ` <20170905181733.GD10851-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-09-08 20:16 ` Melroch
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=20170905045318.GE3765@Johns-MacBook-Pro.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).