From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: docbook codeblock callouts > markdown
Date: Wed, 23 Nov 2022 18:34:56 +0100 [thread overview]
Message-ID: <8735a9po3h.fsf@zeitkraut.de> (raw)
In-Reply-To: <99430384-ef3a-4534-a9da-8dcbcf7f0f91n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Aidan Reilly <aireilly-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
> A feature of docbook/asciidoc that is really useful is codeblock
> callouts. It seems that this is not currently supported in the latest
> pandoc.
I didn't know about callouts, they seem like a nice and useful feature:
https://docs.asciidoctor.org/asciidoc/latest/verbatim/callouts/
Could you post the DocBook code generated by asciidoctor? I suspect that
this feature would require changes to the docbook reader, but maybe once
could make do with a custom Lua reader.
> Is there a way to tell pandoc to passthrough codeblocks "untouched"?
> I think if this was the case a lua filter could apply the rest of the
> markup I need.
>
> Example:
> $ cat callout.adoc
> [source,yaml]
> ----
> bmc:
> address: <bmc_address>
> credentialsName: <secret_credentials_name> <1>
> disableCertificateVerification: True
> ----
> <1> `credentialsName` needs a callout>
>
> Run through asciidoctor > pandoc:
>
> $ asciidoctor -b docbook -o - callout.adoc | pandoc -t markdown -f
> docbook
> ``` yaml
> bmc:
> address: <bmc_address>
> credentialsName: <secret_credentials_name>
> disableCertificateVerification: True
> ```
>
> - `credentialsName` needs a callout
>
> Any other suggestions or strategies welcome
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-11-23 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 9:03 Aidan Reilly
[not found] ` <99430384-ef3a-4534-a9da-8dcbcf7f0f91n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-23 17:34 ` Albert Krewinkel [this message]
[not found] ` <8735a9po3h.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-25 10:24 ` Aidan Reilly
[not found] ` <7925cbe1-1d0d-4b9f-abe4-9224472bd417n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-01 16:57 ` Aidan Reilly
[not found] ` <42d817a7-49f5-452a-a38c-d0764ec3e5cdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-03 8:16 ` Albert Krewinkel
[not found] ` <87tu2cx5k6.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-03 10:13 ` Aidan Reilly
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=8735a9po3h.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).