From: christophe dervieux <christophe.dervieux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Format supported for pandoc.RawBlock() and `raw_attributes`
Date: Thu, 25 May 2023 06:11:57 -0700 (PDT) [thread overview]
Message-ID: <8f73cb8b-cd69-4f3a-805b-e63d8b2a1dbdn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1315 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 6932 bytes --]
next reply other threads:[~2023-05-25 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 13:11 christophe dervieux [this message]
[not found] ` <8f73cb8b-cd69-4f3a-805b-e63d8b2a1dbdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-29 19:00 ` 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=8f73cb8b-cd69-4f3a-805b-e63d8b2a1dbdn@googlegroups.com \
--to=christophe.dervieux-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).