public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Aidan Reilly <aireilly-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: docbook codeblock callouts > markdown
Date: Thu, 1 Dec 2022 08:57:34 -0800 (PST)	[thread overview]
Message-ID: <42d817a7-49f5-452a-a38c-d0764ec3e5cdn@googlegroups.com> (raw)
In-Reply-To: <7925cbe1-1d0d-4b9f-abe4-9224472bd417n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 3619 bytes --]

Wondering about this again. Albert, are you suggesting something like a 
custom docbook reader might be useful 
here? https://pandoc.org/custom-readers.html Are thee examples of custom 
docbook readers you can point to? 

Thanks,

Aidan

On Friday, November 25, 2022 at 10:24:13 AM UTC Aidan Reilly wrote:

> Hi Albert!
>
> So here is the complete example: 
>
> $ cat callout.adoc
> [source,yaml]
> ----
> bmc:
>   address: <bmc_address>
>   credentialsName: <secret_credentials_name>  <1>
>   disableCertificateVerification: True
> ----
> <1> `credentialsName` needs a callout
>
>
> $ cat callout.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <?asciidoc-toc?>
> <?asciidoc-numbered?>
> <article xmlns="http://docbook.org/ns/docbook" xmlns:xl="
> http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
> <info>
> <title>Untitled</title>
> <date>2022-11-25</date>
> </info>
> <programlisting language="yaml" linenumbering="unnumbered">bmc:
>   address: &lt;bmc_address&gt;
>   credentialsName: &lt;secret_credentials_name&gt;  <co xml:id="CO1-1"/>
>   disableCertificateVerification: True</programlisting>
> <calloutlist>
> <callout arearefs="CO1-1">
> <para><literal>credentialsName</literal> needs a callout</para>
> </callout>
> </calloutlist>
> </article>
>
>
> $ pandoc -t markdown -f docbook callout.xml
> ``` yaml
> bmc:
>   address: <bmc_address>
>   credentialsName: <secret_credentials_name>  
>   disableCertificateVerification: True
> ```
>
> -   `credentialsName` needs a callout
>
> I'm just not clear whether this can be handled with a lua filter or not.
>
> Thanks,
>
> Aidan
>
> On Wednesday, November 23, 2022 at 5:39:22 PM UTC Albert Krewinkel wrote:
>
>>
>> Aidan Reilly <aire...-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 
>>
>

-- 
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/42d817a7-49f5-452a-a38c-d0764ec3e5cdn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5816 bytes --]

  parent reply	other threads:[~2022-12-01 16:57 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
     [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 [this message]
     [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=42d817a7-49f5-452a-a38c-d0764ec3e5cdn@googlegroups.com \
    --to=aireilly-h+wxahxf7alqt0dzr+alfa@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).