public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jasper Timmer <jjwtimmer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: how to implement callouts in docbook -> markdown
Date: Mon, 30 May 2022 11:57:15 -0700 (PDT)	[thread overview]
Message-ID: <0748d081-5c90-4212-99e2-98b70cfc1da2n@googlegroups.com> (raw)
In-Reply-To: <ed4ffa93-0bb1-4e47-9f23-7e81f0fd63dfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

by the way:
callouts: https://docs.asciidoctor.org/asciidoc/latest/verbatim/callouts/ 

in docbook XML it looks like this:

----
<title>Examples</title>
<para>
<programlisting language="rascal" linenumbering="unnumbered">module 
demo::basic::Quine

import IO;
import String;

void quine(){
  println(program); *<co xml:id="CO4-1"/>*
  println("\"" + escape(program, ("\"" : "\\\"", "\\" : "\\\\")) + "\";"); *<co 
xml:id="CO4-2"/>*
}

str program = *<co xml:id="CO4-3"/>*
"module demo::basic::Quine

import IO;
import String;

void quine(){
  println(program);
  println(\"\\\"\" + escape(program, (\"\\\"\" : \"\\\\\\\"\", \"\\\\\" : 
\"\\\\\\\\\")) + \"\\\";\");
}

str program ="; <co xml:id="CO4-4"/></programlisting>
</para>
</formalpara>
*<calloutlist>*
*<callout arearefs="CO4-3">*
<para>A remarkable point in the code: the string variable 
<literal>program</literal> has as value
the text of the module <literal>Quine</literal> upto here.</para>
*</callout>*
----

Op maandag 30 mei 2022 om 20:50:29 UTC+2 schreef Jasper Timmer:

> I'm trying to convert some asciidoc documentation to markdown. I found 
> this snippet online: 
> https://tinyapps.org/blog/201701240700_convert_asciidoc_to_markdown.html
>
> works pretty darn well :) only callouts are not preserved. They just 
> completely disappear. How can I fix that?
>
> I installed latest deb from github.
>
> Thanks! 
> Jasper
>

-- 
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/0748d081-5c90-4212-99e2-98b70cfc1da2n%40googlegroups.com.

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

      parent reply	other threads:[~2022-05-30 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 18:50 Jasper Timmer
     [not found] ` <ed4ffa93-0bb1-4e47-9f23-7e81f0fd63dfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-30 18:57   ` Jasper Timmer [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=0748d081-5c90-4212-99e2-98b70cfc1da2n@googlegroups.com \
    --to=jjwtimmer-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).