From: Brad Dixon <rbdixon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Markdown reader irregularity parsing tables in YAML metadata blocks
Date: Thu, 26 Apr 2018 11:53:44 -0700 (PDT) [thread overview]
Message-ID: <5a5dc27e-6645-4efc-8dc7-8c11af64897d@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1731 bytes --]
Hi:
* version: pandoc 2.1.3, duplicated on pandoc HEAD
* files: https://gist.github.com/rbdixon/490e2bc39be0b93efc2bc79ade5d497b
I put tables in YAML metadata blocks as multiline strings to aid
integration of tools that generate Markdown that is then processed by
Pandoc. I've been chasing an odd behavior that I've narrowed down to
pandoc's paring of tables in YAML metadata blocks.
This example (test_passes.md) works:
---
table: |-
Table: Title
| A | B |
|:--|:--|
| A | B |
| A | B |
| A | B |
x
...
Text
When I inspect the Pandoc JSON I see that it has parsed a table with a
header and three rows. This example (test_fails.md) does not work:
---
table: |-
Table: Title
| A | B |
|:--|:--|
| A | B |
| A | B |
| A | B |
...
Text
The difference is the removal of "\nx\n" at the end of the multiline
string. When I inspect the Pandoc JSON the last row of the table is split
off into its own `Plain` stanza rather than being included, as expected, in
the `Table` stanza.
Any advice on what I might be doing wrong here? Perhaps I'm abusing
multiline strings and their markdown interpretation a bit.
Thanks,
Brad
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5a5dc27e-6645-4efc-8dc7-8c11af64897d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2679 bytes --]
next reply other threads:[~2018-04-26 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 18:53 Brad Dixon [this message]
[not found] ` <5a5dc27e-6645-4efc-8dc7-8c11af64897d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-04-26 19:47 ` 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=5a5dc27e-6645-4efc-8dc7-8c11af64897d@googlegroups.com \
--to=rbdixon-re5jqeeqqe8avxtiumwx3w@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).