From: Jim Pryor <jim.pryor.nyu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Multiple paragraph <li> under <dd> in commonmark_x
Date: Mon, 22 Aug 2022 07:57:48 -0700 (PDT) [thread overview]
Message-ID: <fe0dab8e-b982-4742-a4fd-b683df1fbdeen@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1926 bytes --]
I may be abusing definition lists, but I regularly use them with the `<dt>`
being a date of a blog-like entry, and then the `<dd>` being the body. This
results in me often needing multi-paragraph `<dd>`s.
Just doing that is very feasible:
```
> printf -- 'term\n: Para1\n\n Para2\n\nRest' | pandoc -f commonmark_x
-t native
[ DefinitionList
[ ( [ Str "term" ]
, [ [ Plain [ Str "Para1" ] , Plain [ Str "Para2" ] ] ]
)
]
, Para [ Str "Rest" ]
]
```
But today I needed the `<dd>` to contain an `<ol>` with a multi-paragraph
`<li>`, and this is not working:
```
> printf -- 'term\n: 1. Para1\n\n Para2\n\nRest' | pandoc -f
commonmark_x -t native
[ DefinitionList
[ ( [ Str "term" ]
, [ [ OrderedList
( 1 , Decimal , Period ) [ [ Plain [ Str "Para1" ] ] ]
, Plain [ Str "Para2" ]
]
]
)
]
, Para [ Str "Rest" ]
]
```
If I indent the `Para2` any further it becomes a CodeBlock.
Is there anyway to markup this text that would (or at least should, perhaps
in some later revision of pandoc) enable me to get:
```
[ DefinitionList
[ ( [ Str "term" ]
, [ [ OrderedList
( 1 , Decimal , Period ) [ [ Plain [ Str "Para1" ], Plain [
Str "Para1" ]] ]
]
]
)
]
, Para [ Str "Rest" ]
```
Or should I just stop trying to include such complex content in a `<dd>`?
(and presumably get the layout I'm looking for with css classes instead).
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/fe0dab8e-b982-4742-a4fd-b683df1fbdeen%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3176 bytes --]
next reply other threads:[~2022-08-22 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 14:57 Jim Pryor [this message]
[not found] ` <fe0dab8e-b982-4742-a4fd-b683df1fbdeen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-08-22 16:20 ` John MacFarlane
[not found] ` <FB882D3D-4E80-422C-BA07-B720C3C140CF-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-08-22 16:31 ` Jim Pryor
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=fe0dab8e-b982-4742-a4fd-b683df1fbdeen@googlegroups.com \
--to=jim.pryor.nyu-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).