From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Specifying Raw Block Elements
Date: Tue, 10 Oct 2017 09:24:06 -0700 [thread overview]
Message-ID: <20171010162406.GE70978@protagoras> (raw)
In-Reply-To: <ae0ccc2e-6c5c-4d64-9a0f-33f27b8e028b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
In the dev version, you can specify raw blocks or inline for
a given output format:
```{=html}
This is an HTML block.
```
And `this is inline HTML`{=html}.
+++ Saivan Hamama [Oct 09 17 19:57 ]:
> It seems almost all of the issues I've been wrestling with for the last
> two days are stemming from this problem. Is it possible to have a way
> to specify that we want to pass html verbatim, without having pandoc
> modify it at all? It seems that particular tags have been excluded, but
> having a Block level object that allows us to input html would be a
> godsend!
> Is there some reason why this wouldn't work? Maybe something as simple
> as:
> <<>>
> ... html goes here
> <<>>
> Or even a command line option that allows us to specify which tags we
> don't want pandoc to treat as verbatim blocks?
> Eg, Svg's, myowncanvas above etc (which can be set along with the
> default ones provided in pandoc)
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/ae0ccc2e-6c5c-4d64-
> 9a0f-33f27b8e028b%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/ae0ccc2e-6c5c-4d64-9a0f-33f27b8e028b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-10-10 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 3:58 Saivan Hamama
[not found] ` <bed5a293-ddf6-4ef6-9e8c-c55f5e4aced2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-10 2:57 ` Saivan Hamama
[not found] ` <ae0ccc2e-6c5c-4d64-9a0f-33f27b8e028b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-10 16:24 ` John MACFARLANE [this message]
2017-10-11 0:52 ` Saivan Hamama
[not found] ` <f81758a8-93c5-4d35-bb61-d4255d248339-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-11 0:53 ` Saivan Hamama
2017-10-11 3:36 ` John MacFarlane
[not found] ` <20171011033629.GA29983-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-12 3:58 ` Saivan Hamama
[not found] ` <ce0b4c71-f89e-48ce-a0f1-d49f4edebbf0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-12 15:08 ` 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=20171010162406.GE70978@protagoras \
--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).