From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Format supported for pandoc.RawBlock() and `raw_attributes`
Date: Mon, 29 May 2023 12:00:29 -0700 [thread overview]
Message-ID: <9DDA1053-7495-4806-9028-E3B218A0B51F@gmail.com> (raw)
In-Reply-To: <8f73cb8b-cd69-4f3a-805b-e63d8b2a1dbdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
I think you could open an issue for this.
> On May 25, 2023, at 6:11 AM, christophe dervieux <christophe.dervieux@gmail.com> wrote:
>
> From documentation, it is not clear to me what is the format supported for pandoc.RawBlock and raw_attributes
>
> For raw_attributes, doc says https://pandoc.org/MANUAL.html#extension-raw_attribute
>
> The format name should match the target format name (see -t/—to, above, for a list, or use pandoc —list-output-formats)
>
> and pandoc.RawBlock only says format of content.
>
> I would think that pandoc.RawBlock(FORMAT, text) would work, but FORMAT is
>
> The global FORMAT is set to the format of the pandoc writer being used (html5, latex, etc.), so the behavior of a filter can be made conditional on the eventual output format.
>
> but it seems this don’t work in some case like reveajs
>
> ```{=revealjs}
> content
> ```
>
> does not get included in output, only using html works. Same with pandoc.RawBlock
>
> Is this expected ? Or is this an issue to report ?
>
> Thank you
>
>
> --
> 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/8f73cb8b-cd69-4f3a-805b-e63d8b2a1dbdn%40googlegroups.com.
--
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/9DDA1053-7495-4806-9028-E3B218A0B51F%40gmail.com.
prev parent reply other threads:[~2023-05-29 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 13:11 christophe dervieux
[not found] ` <8f73cb8b-cd69-4f3a-805b-e63d8b2a1dbdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-29 19:00 ` John MacFarlane [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=9DDA1053-7495-4806-9028-E3B218A0B51F@gmail.com \
--to=fiddlosopher-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).