From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [Spam] line with only raw_attributes content still gets wrap in <p>: is this expected ?
Date: Thu, 16 Dec 2021 10:12:35 -0500 [thread overview]
Message-ID: <0f498ce5-eac5-b101-d1c9-08f42c3c0359@usa.net> (raw)
In-Reply-To: <fe4cbfa7-465e-4328-8bf3-3e1c178845ddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On 12/16/21 4:59 AM, christophe dervieux wrote:
> Hi,
>
> I am not sure if this is expected behavior or not, so not sure to open
> an issue or a feature request.
>
> Currently, with |raw_attributes| extentions, we can include raw HTML.
> When using a one line we could use this form
>
> |Including an iframe `<iframe
> src="https://example.org"></iframe>`{=html} Other content below |
>
> However, this will be wrapped in |<p>| tag. Pandoc will produce
>
> |<p>Including an iframe</p> <p><iframe
> src="https://example.org"></iframe></p> <p>Other content below</p> |
>
> I would expect to have my HTML code preserved and not wrapped.
>
> I know I could use
>
> |Including an iframe ```{=html} <iframe
> src="https://example.org"></iframe> ``` Other content below |
>
> to produce
>
> |<p>Including an iframe</p> <iframe src="https://example.org"></iframe>
> <p>Other content below</p> |
>
> Is this the expected way then ? Or should the former also no wrap when
> the all line is a content with raw_attributes
From the docs, I'd say that's expected: The first form is an *inline*
block, and the latter is just a block. This would correspond to HTML's
inline and block elements - the former of which would always need to be
inside a block.
Markdown takes a whitespace-separated line as a paragraph, so that first
is a paragraph with a single inline element. The second is a block itself.
This interpretation also allows you to do things like have a paragraph
completely covered in a span, etc. If you want an HTML block, use the
block format.
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
prev parent reply other threads:[~2021-12-16 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 9:59 christophe dervieux
[not found] ` <fe4cbfa7-465e-4328-8bf3-3e1c178845ddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-16 15:12 ` Daniel Staal [this message]
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=0f498ce5-eac5-b101-d1c9-08f42c3c0359@usa.net \
--to=dstaal-jdbf3xikgs8@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).