Markdown reader irregularity parsing tables in YAML metadata blocks

Markdown reader irregularity parsing tables in YAML metadata blocks

[Brad Dixon]

[-- 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 --]

Re: Markdown reader irregularity parsing tables in YAML metadata blocks

[John MacFarlane]

I usually use `|` rather than `|-`.
These are very similar in YAML, but `|-` will not include a
final newline, and I think that explains what you're seeing.

Brad Dixon <rbdixon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> 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.